On Jan 23, 2014 1:12 PM, "Stephen Gallagher" <sgall...@redhat.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/23/2014 01:43 PM, Kevin Kofler wrote: > > Christopher Meng wrote: > >> But you can do this on copr IMO. Also update-testing is not just > >> a place for updates to have a break, you can let it satisfy the > >> needs of testing for unstable. > > > > Well, that's kinda abusing updates-testing. IMHO, COPR is the much > > better option until you have something reasonably close to going > > stable. > > > > The other problem with using updates-testing in this way is that it > makes it more difficult if you have to deliver a real bug or security > fix to stable. Now you have to unpush your testing version, mangle > your git history, file a new update ... > > > I agree with Kevin that this is pretty much exactly what COPR is good > at (and what I'm using it for myself[1]). > > 1) http://copr.fedoraproject.org/coprs/sgallagh/ReviewBoard2/ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlLhd8QACgkQeiVVYja6o6N1WgCgqGU51RjTv4/uizYPOV5HSBhE > WFkAoLAl4Twg3iHIBgEx1O5++juLlaXH > =rNyt > -----END PGP SIGNATURE----- > --
Is there something inherent to COPRs that solves the problem of duplicate paths, ie /usr/bin/mercurial from two different sources? If I missed something, a link with an appropriate measure of mocking would be welcome. --Pete
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
