Re: [gentoo-dev] Re: Let's redesign the entire filesystem!
On Thu, Mar 15, 2012 at 04:44:11PM -0400, Richard Yao wrote > Busybox is installed as part of the system profile on amd64. You can > install mdev by doing this: > > ln -s /bin/busybox /sbin/mdev The official method is to build busybox with the "mdev" USE flag. That is the only way that virtual/dev-manager recognizes it, and doesn't try to pull in udev, instead. From the ebuild... RDEPEND="|| ( sys-fs/udev sys-apps/busybox[mdev] sys-fs/devfsd sys-fs/static-dev sys-freebsd/freebsd-sbin )" > There is documentation in the busybox GIT for how to use it: > > http://git.busybox.net/busybox/plain/docs/mdev.txt TOOT!!! (blowing my own horn). See http://www.waltdnes.org/mdev/ for instructions on replacing udev with mdev for simple Gentoo systems. Hopefully more info will start arriving, allowing more complex systems to work with mdev. -- Walter Dnes
Re: [gentoo-dev] gentoo-news repository migrated to git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 03/15/2012 07:49 PM, Ulrich Mueller wrote: >> On Thu, 15 Mar 2012, Rich Freeman wrote: > >>> The gentoo-news repository has moved from subversion to git >>> some time ago. New news items should be committed to git only, >>> because the master rsync doesn't pull from the svn repository >>> any more. > >> Is there a link to the repository anywhere? I don't see one on >> g.o, but I might not be looking in the right place. > >> Might not hurt to include instructions on how to push to it as >> well... > > Sorry, I should have mentioned that of course. > > git://anongit.gentoo.org/proj/gentoo-news.git > git+ssh://g...@git.gentoo.org/proj/gentoo-news.git > > Ulrich > Could you please prepare a patch for http://devmanual.gentoo.org/general-concepts/news/index.html ? - -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iQIcBAEBCgAGBQJPZFemAAoJEPqDWhW0r/LCQ8wP/i2ucp7NslDoE6UaEfr8DyQF nGXXUR6+DkUNG8DDlTQ1pNAhTEaDND7b17itQ2SjIXVHN6XNdXynsYOI4PxbOReG 78rBnA/dyIJeI70V/SWnkP+A5TVvi9V/klBMnzq+NPjerBMg0Xiz5GM9yvliM0cu czTdhn+mEOBLXAIe6T42aWkxX8a498z2itoyXBPnIfgaylhY6tNt++i4eSQFzfPY rf/CoZfh1TIBhcJ6U7Q2sBtsLKswmpmqsFJ52JEk5rPzAd8kj5/Z3WUCPY95RHvl MO5lGcAULL2WLOUy1n41wEkYrMLQSPPGViBvuu4ISWAkVxlhBbzZm0Fgmu9WpqUi Edu4HY/9w0gew/ZxzYDtfAj+8J6uc5/ShESgNczbEuLcsu0CckOuf8oUn24A5BCh yFpZ8cGNVz/AOM6Iuy/wKfSIbljWM/PUkD3jJPW7LWjny/SoV6mrJPLdAlb5cKTg yHasDO7Zk+oXon/Od94QKv+qOyWAg0ArRh+69oBZq8lG9WgZ/smUV6EBg3X9mAjd /bWwk2pJI9x8qEUSyVr8EqDg/H3bPAegh7ET2xqxW8wfK7qlI2PbaVgOHjtB+FIU 8bz8pMjtpmsrSXVryCKKCzHJsR7UOzRLBlD7rNP3cIBl23IzpkXpLPZdUQgZOKpG o3rScc/vmO6h3sbDVpjY =yptJ -END PGP SIGNATURE-
[gentoo-dev] Change USE flags when compiling with FEATURES=test
So you run set FEATURES=test to run a package's test suite during keywording. Later, you emerge -vuNDa ... and portage wants to reemerge that package with USE=-test. Can't we avoid this somehow? I presume in the vast majority of cases emerging with FEATURES/USE=test doesn't actually affect what's installed. I'd guess we'd need to be able to remove 'test' from the set of IUSE and have a new helper function to check if 'test' is in FEATURES? Matt
Re: [gentoo-dev] Change USE flags when compiling with FEATURES=test
On Sat, 17 Mar 2012 15:33:42 -0400 Matt Turner wrote: > So you run set FEATURES=test to run a package's test suite during > keywording. Later, you emerge -vuNDa ... and portage wants to reemerge > that package with USE=-test. > > Can't we avoid this somehow? I presume in the vast majority of cases > emerging with FEATURES/USE=test doesn't actually affect what's > installed. > > I'd guess we'd need to be able to remove 'test' from the set of IUSE > and have a new helper function to check if 'test' is in FEATURES? If you want that, USE_EXPAND_IGNORE_CHANGES, like USE_EXPAND_HIDDEN, would be cleaner. 'test' is already too special. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] Change USE flags when compiling with FEATURES=test
On 18 March 2012 08:33, Matt Turner wrote: > So you run set FEATURES=test to run a package's test suite during > keywording. Later, you emerge -vuNDa ... and portage wants to reemerge > that package with USE=-test. > > Can't we avoid this somehow? I presume in the vast majority of cases > emerging with FEATURES/USE=test doesn't actually affect what's > installed. Not so, there are a lot of things where USE="test" pulls in extra dependencies, dev-perl/* is rife with them. And I've seen some things where USE=test changes behaviour of the compile phase sufficient that enabling USE=test *could* change the code compiled as well. But I think I see where you're comming from. I just can't see a reasonable cover-all approach that wouldn't really be a large nasty package-manager specific hack. > I'd guess we'd need to be able to remove 'test' from the set of IUSE > and have a new helper function to check if 'test' is in FEATURES? And besides, I'll reinstall a package if so much as the MD5 changes due to somebody adding keywording for an arch I don't use ;) I think what would be more practical is a sane way to enable FEATURES="" on a per-package level like USE flags in portage, then you could enable FEATURES="test" for that one package and it would always build that package with USE="test" Paludis does this already via an extended use.conf syntax: =dev-foo/bar-1.2 flag -otherflag BUILD_OPTIONS: optional_tests LINGUAS: en Perhaps portage does this already and I'm hiding under a rock, but I haven't seen it, and I've just cheated the system with linguas_en and other similar manual USE_EXPAND tricks in my package.use -- Kent perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
Re: [gentoo-dev] Change USE flags when compiling with FEATURES=test
On 03/17/12 15:43, Kent Fredric wrote: > On 18 March 2012 08:33, Matt Turner wrote: >> So you run set FEATURES=test to run a package's test suite during >> keywording. Later, you emerge -vuNDa ... and portage wants to reemerge >> that package with USE=-test. >> >> Can't we avoid this somehow? I presume in the vast majority of cases >> emerging with FEATURES/USE=test doesn't actually affect what's >> installed. > > Not so, there are a lot of things where USE="test" pulls in extra > dependencies, dev-perl/* is rife with them. > > And I've seen some things where USE=test changes behaviour of the > compile phase sufficient that enabling USE=test *could* change the > code compiled as well. To expand on this, I know that sys-devel/gcc will save a report of the make check results to the filesystem when FEATURES=test is enabled. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Change USE flags when compiling with FEATURES=test
On Sat, 2012-03-17 at 15:33 -0400, Matt Turner wrote: > So you run set FEATURES=test to run a package's test suite during > keywording. Later, you emerge -vuNDa ... and portage wants to reemerge > that package with USE=-test. > > Can't we avoid this somehow? I presume in the vast majority of cases > emerging with FEATURES/USE=test doesn't actually affect what's > installed. > > I'd guess we'd need to be able to remove 'test' from the set of IUSE > and have a new helper function to check if 'test' is in FEATURES? Typically "test" is added to IUSE only when building and/or running the test suite requires specifying additional dependencies. So if we remove "test" from IUSE, we would need to allow DEPEND to have FEATURES-based conditionals. Which would probably mean a new EAPI. I think the easier solution is to modify portage to ignore changes in the "test" USE flag when doing "emerge --newuse". -Alexandre.
Re: [gentoo-dev] Change USE flags when compiling with FEATURES=test
On 03/17/2012 12:51 PM, Alexandre Rostovtsev wrote: > I think the easier solution is to modify portage to ignore changes in > the "test" USE flag when doing "emerge --newuse". Yes, that's part of the plan [1] discussed in bug #373209. [1] https://bugs.gentoo.org/show_bug.cgi?id=373209#c3 -- Thanks, Zac
