On Thu, Sep 22, 2011 at 10:25:06PM +0200, Bill Allombert wrote:
> > I know that the buildd system likes to pull in the first package in
> > such an alternative dependency chain. And now I start to wonder:
> > Is it allowed for a package in main to have a package _outside_ of main
> > as first c
On Tue, Sep 20, 2011 at 01:12:37PM +0200, Gerfried Fuchs wrote:
> Hi!
>
> Policy is clear on packages in main aren't allowed to depend on
> packages outside of main. Now in a fair amount of cases this has been
> worked around by having the package outside of main as alternative
> depende
On 20/09/11 06:24 PM, Paul Wise wrote:
> In my intended case I believe they always end up with foo from main,
> only if they choose foo-contrib will they get it, which is how I think
> it should be. main should not reference packages from contrib/non-free
> in any way.
If that's how it works, then
On Tue, Sep 20, 2011 at 8:04 PM, Ben Armstrong wrote:
> While that neatly sidesteps the issue, 7.5 says:
>
> To specify which of a set of real packages should be the default to
> satisfy a particular dependency on a virtual package, list the real
> package as an alternative before the
On 11-09-20 at 07:41pm, Luk Claes wrote:
> On 09/20/2011 01:12 PM, Gerfried Fuchs wrote:
> > Hi!
>
> Hi
>
> > Policy is clear on packages in main aren't allowed to depend on
> > packages outside of main. Now in a fair amount of cases this has
> > been worked around by having the packa
On 09/20/2011 01:12 PM, Gerfried Fuchs wrote:
> Hi!
Hi
> Policy is clear on packages in main aren't allowed to depend on
> packages outside of main. Now in a fair amount of cases this has been
> worked around by having the package outside of main as alternative
> dependency and a packag
On 09/20/2011 08:43 AM, Paul Wise wrote:
> On Tue, Sep 20, 2011 at 7:12 PM, Gerfried Fuchs wrote:
> Package: bar
> Depends: foo
>
> Package: foo-contrib
> Provides: foo
While that neatly sidesteps the issue, 7.5 says:
To specify which of a set of real packages should be the default to
On Tue, Sep 20, 2011 at 7:12 PM, Gerfried Fuchs wrote:
> tl;dr - what do you think, is a "Depends: foo-contrib | foo" acceptable
> for packages in main or should it be "Depends: foo | foo-contrib"
> instead?
I vote:
Package: bar
Depends: foo
Package: foo-contrib
Provides: foo
--
bye,
pabs
h
Hi!
Policy is clear on packages in main aren't allowed to depend on
packages outside of main. Now in a fair amount of cases this has been
worked around by having the package outside of main as alternative
dependency and a package in main offer basic functionality for the
package to still
9 matches
Mail list logo
