[gentoo-dev] Re: [RFC] SRC_URI behaviour

[Michael Palimaka]

On 16/06/2013 10:24, Zac Medico wrote:

How about it we add a src_fetch phase, so that the VCS intricacies can
be delegated to ebuilds/eclasses (like they are now, but without having
to abuse src_unpack). If we include a way for src_fetch to communicate
changes in VCS revisions to the package manager, then we'll be able to
integrate functionality like smart-live-rebuild directly into the
package manager (as discussed in bug 182028 [1]).

[1] http://bugs.gentoo.org/show_bug.cgi?id=182028


This sounds interesting. It definitely would be nice to have proper 
package manager support for VCS.


I don't think that this will somehow legitimise live ebuilds. We use 
policies to prevent inappropriate things from entering the tree, not by 
preventing tools that might facilitate it.


Best regards,
Michael

[gentoo-dev] Re: [RFC] SRC_URI behaviour

[Michael Palimaka]

On 15/06/2013 23:47, Ulrich Mueller wrote:

On Sat, 15 Jun 2013, Diego Elio Pettenò wrote:



restrict+http: (as suggested by the OP) is probably not enough
because it doesn't distinguish between fetch and mirror
restriction.



nofetch+http and nomirror+http ?


Or the other way around: {fetch,mirror}+http. I'd rather have RESTRICT
apply to all of SRC_URI (as it is now) and use the new syntax to
specify any exceptions from the restriction.

Ulrich




I like this idea.

Best regards,
Michael