On Tue, Jul 22, 2014, at 05:40 PM, Matthew Miller wrote: > On Tue, Jul 22, 2014 at 08:07:39AM -0400, Colin Walters wrote: > > In the meantime though, Atomic still needs a mechanism to *try* code > > that's in development. So I may look at having the internal compose > > server be a "pull from COPR" type thing and thus be a remix (again), but > > improve on the current situation by mirroring to dl.fp.org or so. > > Is Rawhide too divergent, or too fast moving? One problem is that Rawhide is still post package review. For mainline, COPR has been a massive release value for testing inbound code - take the example of etcd that I'm working on right now[1] There are people that are trying to iterate on *actually using* etcd, while I'm simultaneously trying to de-bundle and update the package. On a mainline system, you can take stock Fedora and add the COPR - it works well. But for Atomic, the tree has to be composed *as a unit* - and such a tree containing COPR code would then (to my understanding) be required to be a Remix. This type of thing is yet another reason to support local package layering - the current state is definitely one of the negative tradeoffs for the atomic updates in the current architecture. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1047194 http://copr.fedoraproject.org/coprs/walters/atomic-next/ _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
