Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Adam Williamson
On Thu, 2014-01-23 at 19:19 -0700, Pete Travis wrote: > 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. Not AFAIK. If

Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Pete Travis
On Jan 23, 2014 1:12 PM, "Stephen Gallagher" 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 c

Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Christopher Meng
On Jan 24, 2014 7:14 AM, "Adam Williamson" wrote: > In other words: Christopher, if you're currently doing this, please move > the packages to a COPR or other venue more appropriate for this purpose, > and stop doing it. No absolutely not. I don't have any thing *unstable*. Something unstable ar

Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Adam Williamson
On Thu, 2014-01-23 at 15:11 -0800, Adam Williamson wrote: > On Thu, 2014-01-23 at 19:43 +0100, 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 testi

Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Adam Williamson
On Thu, 2014-01-23 at 19:43 +0100, 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-testi

Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Stephen Gallagher
-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, t

Re: What to do about packaging beta, or rc as alternate installable

2014-01-23 Thread Kevin Kofler
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

Re: What to do about packaging beta, or rc as alternate installable

2014-01-22 Thread Richard W.M. Jones
On Tue, Jan 21, 2014 at 07:33:40PM -0500, Neal Becker wrote: > One of the packages I maintain is mercurial. Frequently (e.g., now), there > is a rc version available for test. It will probably break some other package > that depends on it. > > I am thinking of a model like google uses for chrome

Re: What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Adam Williamson
On Tue, 2014-01-21 at 19:33 -0500, Neal Becker wrote: > One of the packages I maintain is mercurial. Frequently (e.g., now), there > is a rc version available for test. It will probably break some other package > that depends on it. > > I am thinking of a model like google uses for chrome. I co

Re: What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Christopher Meng
On Jan 22, 2014 10:03 AM, "Mauricio Tavares" wrote: > Still, it makes sense to have a place to beta test either the > package or the packaging (how to create a proper package?) itself. It's hard to say how to create a proper package testing in one slot of pkgdb. Also it may be a burden when

Re: What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Adam Williamson
On Tue, 2014-01-21 at 21:03 -0500, Mauricio Tavares wrote: > On Tue, Jan 21, 2014 at 8:58 PM, Christopher Meng wrote: > > Seriously, it's harmful to provide unstable packages to users. > > > Still, it makes sense to have a place to beta test either the > package or the packaging (how to crea

Re: What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Mauricio Tavares
On Tue, Jan 21, 2014 at 8:58 PM, Christopher Meng wrote: > Seriously, it's harmful to provide unstable packages to users. > Still, it makes sense to have a place to beta test either the package or the packaging (how to create a proper package?) itself. > And I don't think Fedora has a long

Re: What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Christopher Meng
Seriously, it's harmful to provide unstable packages to users. And I don't think Fedora has a long term support. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Josh Boyer
On Tue, Jan 21, 2014 at 7:33 PM, Neal Becker wrote: > One of the packages I maintain is mercurial. Frequently (e.g., now), there > is a rc version available for test. It will probably break some other package > that depends on it. > > I am thinking of a model like google uses for chrome. I coul

What to do about packaging beta, or rc as alternate installable

2014-01-21 Thread Neal Becker
One of the packages I maintain is mercurial. Frequently (e.g., now), there is a rc version available for test. It will probably break some other package that depends on it. I am thinking of a model like google uses for chrome. I could install any of: google-chrome-{stable,beta,unstable} I don