# emergefromgentoox86 -va youtube-dl * Repository: /newaches/gentoo/cvs/gentoo-x86/ These are the packages that would be merged, in order: [ebuild U ~] net-misc/youtube-dl-2013.06.34.2 [2013.06.34] USE="offensive* {-test*}" PYTHON_SINGLE_TARGET="python2_7 -python2_5 -python2_6 -python3_3%" PYTHON_TARGETS="python2_7 -python2_5 -python2_6 -python3_3%" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] [...] >>> Source compiled. make -j5 test #nosetests --with-coverage --cover-package=youtube_dl --cover-html --verbose --processes 4 test nosetests --verbose test test_justin_tv_channelid_matching (test_all_urls.TestAllURLsMatching) ... ok test_justin_tv_chapterid_matching (test_all_urls.TestAllURLsMatching) ... ok test_justintv_videoid_matching (test_all_urls.TestAllURLsMatching) ... ok test_youtube_channel_matching (test_all_urls.TestAllURLsMatching) ... ok test_youtube_extract (test_all_urls.TestAllURLsMatching) ... ok test_youtube_matching (test_all_urls.TestAllURLsMatching) ... ok test_youtube_playlist_matching (test_all_urls.TestAllURLsMatching) ... ok test_ARD (test_download.TestDownload) ... ok test_Bandcamp (test_download.TestDownload) ... ok It does run the test phase, but it suggests that it is not going to do this.
Forgot to mention that emergefromgentoox86 does this: PORTDIR_OVERLAY=${CVS_GENTOO_X86} \ emerge --package-moves=n -v --nodeps Maybe that's significant.
It looks like maybe you used bashrc instead of package.env. The correct way to do it would be with package.env like this: echo 'FEATURES="test"' > /etc/portage/env/features_test.conf echo "net-misc/youtube-dl features_test.conf" >> /etc/portage/package.env
No, I don't use bashrc for that. # cat /etc/portage/env/net-misc/youtube-dl FEATURES="${FEATURES} test"
(In reply to Jeroen Roovers from comment #3) > No, I don't use bashrc for that. > > # cat /etc/portage/env/net-misc/youtube-dl > FEATURES="${FEATURES} test" That is bashrc. It's a common source of confusion. You need to use package.env exactly as I've described.
(In reply to Zac Medico from comment #4) > (In reply to Jeroen Roovers from comment #3) > > No, I don't use bashrc for that. > > > > # cat /etc/portage/env/net-misc/youtube-dl > > FEATURES="${FEATURES} test" > > That is bashrc. It's a common source of confusion. You need to use > package.env exactly as I've described. Oh. Maybe portage(5) should be updated? :) Apparently package.env is loaded during depcalc and such, and /etc/portage/env is only sources during build phases? Both configuration mechanisms using /etc/portage/env isn't helping here. /etc/portage/env/ package-specific bashrc files [...] Additional package-specific bashrc files can be created in /etc/portage/env. [...] package.env Per-package environment variable settings. Entries refer to environment files that are placed in the /etc/portage/env/ directory and have the same format as make.conf(5). Format: - comment lines begin with # (no inline comments) - one DEPEND atom per line followed by name(s) of environment file(s) Example: # use environment variables from /etc/portage/env/glibc.conf for the glibc package sys-libs/glibc glibc.conf
Or maybe emerge should not source these files as if they were bash scripts? I don't know.
(In reply to Jeroen Roovers from comment #5) > Oh. Maybe portage(5) should be updated? :) See bug 388781. > Apparently package.env is loaded during depcalc and such, and > /etc/portage/env is only sources during build phases? Right. > Both configuration > mechanisms using /etc/portage/env isn't helping here. Yeah I know. I merged the package.env patches, people assured me that there wouldn't be any confusion because of that. (In reply to Jeroen Roovers from comment #6) > Or maybe emerge should not source these files as if they were bash scripts? > I don't know. It would be a little late to not source those files as bash scripts, since people have been relying on it for years. Actually, the bashrc thing was originally implemented in profiles/base/profile.bashrc a long time ago, and the code has since been migrated into portage itself. *** This bug has been marked as a duplicate of bug 388781 ***
