http://blogs.gentoo.org/zmedico?disp=comments en-US http://backend.userland.com/rss 60 Sat, 02 Aug 2008 02:08:15 +0000 Zac MEDICO [Member] c19938@http://blogs.gentoo.org/ <blockquote>Should note that @live-rebuild may catch packages that inherit those eclasses, but aren't really "live" packages</blockquote><br /> <br /> It might be good to add support for <strong>RESTRICT=live</strong> (with the reverse meaning of what was originally suggested in <a href="http://bugs.gentoo.org/show_bug.cgi?id=233589" rel="nofollow">bug 233589</a>) since it will also be useful for repoman's <strong>LIVEVCS.stable</strong> check. I've just sent an <a href="http://archives.gentoo.org/gentoo-dev/msg_64b83155637bcad67478e2d2af276780.xml" rel="nofollow">RFC email</a> to the gentoo-dev mailing list. Should note that @live-rebuild may catch packages that inherit those eclasses, but aren't really "live" packages

It might be good to add support for RESTRICT=live (with the reverse meaning of what was originally suggested in bug 233589) since it will also be useful for repoman's LIVEVCS.stable check. I've just sent an RFC email to the gentoo-dev mailing list.]]> http://blogs.gentoo.org/zmedico/2008/07/31/live_rebuild_package_set#c19938 Fri, 01 Aug 2008 20:55:31 +0000 Zac MEDICO [Member] c19935@http://blogs.gentoo.org/ Well, the @live-rebuild set is really only intended as an interim solution until <a href="http://bugs.gentoo.org/show_bug.cgi?id=182028" rel="nofollow">bug 182028</a> has been implemented in a future EAPI. See <a href="http://bugs.gentoo.org/show_bug.cgi?id=233589" rel="nofollow">bug 233589</a> for an alternative way that we might implement @live-rebuild using a new RESTRICT value (that doesn't require an EAPI bump). bug 182028 has been implemented in a future EAPI. See bug 233589 for an alternative way that we might implement @live-rebuild using a new RESTRICT value (that doesn't require an EAPI bump).]]> http://blogs.gentoo.org/zmedico/2008/07/31/live_rebuild_package_set#c19935 Fri, 01 Aug 2008 20:09:30 +0000 Jason [Visitor] c19934@http://blogs.gentoo.org/ Some ebuilds are snapshot ebuilds that point to a certain fixed revision, for example:<br /> <br /> ESVN_REPO_URI="svn://mySvnServer/${PN}@{${PV}}"<br /> <br /> This will never need svn updating, but it is pulled in anyway to @live-rebuild. The solution you have is so elegent, though, that it may not be worth it to fix this outside case.
ESVN_REPO_URI="svn://mySvnServer/${PN}@{${PV}}"

This will never need svn updating, but it is pulled in anyway to @live-rebuild. The solution you have is so elegent, though, that it may not be worth it to fix this outside case.]]> http://blogs.gentoo.org/zmedico/2008/07/31/live_rebuild_package_set#c19934 Fri, 01 Aug 2008 04:59:48 +0000 Zac MEDICO [Member] c19933@http://blogs.gentoo.org/ <blockquote>However one things that would be nice (maybe worth a bug in bugzilla?) would be to have a @live-update (or something) that checks to see if upstream repo has been updated since last merge and in that case updates it, leaving the rest to be. That way you can run @live-rebuild if you want to rebuild all of them and @live-update if you only want the updated.</blockquote><br /> <br /> We already have plans to implement this in a future EAPI. See <a href="http://bugs.gentoo.org/show_bug.cgi?id=182028" rel="nofollow">bug 182028</a>. However one things that would be nice (maybe worth a bug in bugzilla?) would be to have a @live-update (or something) that checks to see if upstream repo has been updated since last merge and in that case updates it, leaving the rest to be. That way you can run @live-rebuild if you want to rebuild all of them and @live-update if you only want the updated.

We already have plans to implement this in a future EAPI. See bug 182028.]]> http://blogs.gentoo.org/zmedico/2008/07/31/live_rebuild_package_set#c19933 Fri, 01 Aug 2008 04:55:35 +0000 Xake [Visitor] c19932@http://blogs.gentoo.org/ This will be pretty neat features.<br /> However one things that would be nice (maybe worth a bug in bugzilla?) would be to have a @live-update (or something) that checks to see if upstream repo has been updated since last merge and in that case updates it, leaving the rest to be. That way you can run @live-rebuild if you want to rebuild all of them and @live-update if you only want the updated.<br /> <br /> This becouse on some system (like one of mines where I have to get a big chunk of xorg from git for some upstream bughunting) there could be a lot of packages inheriting git that are not very often are updated upstream and there is no need to rebuild.<br /> I know there are scripts to do this for you but it would be nice to have them all at one place. However one things that would be nice (maybe worth a bug in bugzilla?) would be to have a @live-update (or something) that checks to see if upstream repo has been updated since last merge and in that case updates it, leaving the rest to be. That way you can run @live-rebuild if you want to rebuild all of them and @live-update if you only want the updated.

This becouse on some system (like one of mines where I have to get a big chunk of xorg from git for some upstream bughunting) there could be a lot of packages inheriting git that are not very often are updated upstream and there is no need to rebuild.
I know there are scripts to do this for you but it would be nice to have them all at one place.]]> http://blogs.gentoo.org/zmedico/2008/07/31/live_rebuild_package_set#c19932 Thu, 31 Jul 2008 10:05:01 +0000 egore911 [Visitor] c19929@http://blogs.gentoo.org/ Wow, this is pretty neat! I'm really looking forward to test it! http://blogs.gentoo.org/zmedico/2008/07/31/live_rebuild_package_set#c19929