Re: Deprecating (and deactivation) of an archive feature?!

2008-08-07 Thread Bernhard R. Link
* Joerg Jaspert <[EMAIL PROTECTED]> [080806 20:48]: > currently our archive has the feature(?) that a source package in component a > (like main) can build a binary package in component b (like contrib).[1] > > Now, this feature is blocking (or making it way harder) to do some > database re-designs

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Ben Finney
Charles Plessy <[EMAIL PROTECTED]> writes: > In the end, the contrib category is free software The works in 'contrib' are free software. That's not enough for them to be in 'main', because 'main' is defined as more than just an arbitrary collection of free software. 'main' is the Debian operating

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Russ Allbery
Charles Plessy <[EMAIL PROTECTED]> writes: > In the end, the contrib category is free software, so why not simply > downgrade it as a priority level, lower than "extra"? I'm assuming that you mean doing this instead of keeping it as a separate distribution area. > This would solve the problem fo

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Charles Plessy
Le Wed, Aug 06, 2008 at 10:07:01PM -0300, Stefano Zacchiroli a écrit : > > A user can be rightfully puzzled by such a situation: is the _source_ > package she is downloading part of Debian or not? Hi Stefano, Jörg, and everybody. In the end, the contrib category is free software, so why not simp

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Stefano Zacchiroli
On Thu, Aug 07, 2008 at 01:28:49AM +0100, Adeodato Simó wrote: > I do think that allowing packages in main to provide binaries in contrib > is useful, so I'd like to hear what the benefits would be if we'd agree > to lose it. I have no idea if there are technical benefits in dropping the support f

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Adeodato Simó
* Julien Cristau [Wed, 06 Aug 2008 21:38:00 +0200]: > On Wed, Aug 6, 2008 at 20:47:50 +0200, Joerg Jaspert wrote: > > Now, the idea would be to deprecate this feature, used by 8 packages in > > unstable, dropping complications in the database backend and the pool > > layout which we would want t

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Robert Millan
On Wed, Aug 06, 2008 at 08:47:50PM +0200, Joerg Jaspert wrote: > > But before we take a final decision I want to hear more input on it. So > here are your 5 seconds, please give input. :) To me, this sounds like a step in the right direction to unfuzzy the distinction between Debian itself (main)

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Russ Allbery
Joerg Jaspert <[EMAIL PROTECTED]> writes: > Now, the idea would be to deprecate this feature, used by 8 packages in > unstable, dropping complications in the database backend and the pool > layout which we would want to avoid. > > Yes, it would require those packages to have a new (additional, may

Re: Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Julien Cristau
On Wed, Aug 6, 2008 at 20:47:50 +0200, Joerg Jaspert wrote: > Now, the idea would be to deprecate this feature, used by 8 packages in > unstable, dropping complications in the database backend and the pool > layout which we would want to avoid. > Maybe you could tell us what the benefit of dropp

Deprecating (and deactivation) of an archive feature?!

2008-08-06 Thread Joerg Jaspert
Hi currently our archive has the feature(?) that a source package in component a (like main) can build a binary package in component b (like contrib).[1] Now, this feature is blocking (or making it way harder) to do some database re-designs we want to do for the central archive database, so we lo