Re: architecture-specific dependencies on virtual packages

2012-07-18 Thread Goswin von Brederlow
On Mon, Jul 09, 2012 at 02:00:14PM +0200, David Kalnischkies wrote: > Hi, > > while playing around with the APT code regarding architecture-specific > dependencies I stumbled over the handling of Provides in that context: > > Package: pkga > Status: install ok installed > Architecture: i386 > Pro

Re: architecture-specific dependencies on virtual packages

2012-07-17 Thread Jonathan Nieder
Jonathan Nieder wrote: > David Kalnischkies wrote: >> in this example: >> Package: foobar >> Architecture: amd64 >> Depends: package-bar >> that last line is in fact read as: >> Depends: package-bar:amd64 > > Why? I don't think that would help humans any more than rea

Re: architecture-specific dependencies on virtual packages

2012-07-17 Thread Jonathan Nieder
David Kalnischkies wrote: > in this example: > Package: foobar > Architecture: amd64 > Depends: package-bar > that last line is in fact read as: > Depends: package-bar:amd64 Why? I don't think that would help humans any more than reading it as Depends: package-b

Re: architecture-specific dependencies on virtual packages

2012-07-17 Thread David Kalnischkies
On Tue, Jul 17, 2012 at 6:46 PM, Jonathan Nieder wrote: > Let me try again. I believe that a dependency like this: > > Depends: package-foo:i386 > > is referring to a specific, concrete, non-virtual package package-foo > and it doesn't make sense to allow this to be satisfied by virtual >

Re: architecture-specific dependencies on virtual packages

2012-07-17 Thread Jonathan Nieder
David Kalnischkies wrote: > On Fri, Jul 13, 2012 at 11:36 PM, Jonathan Nieder wrote: >> I agree here. If I understand correctly, you are saying that it would >> be best if a dependency >> >> Package: a >> Depends: phonon-backend >> >> should only be satisfied by a package from an

Re: architecture-specific dependencies on virtual packages

2012-07-17 Thread David Kalnischkies
On Fri, Jul 13, 2012 at 11:36 PM, Jonathan Nieder wrote: > David Kalnischkies wrote: >> As an example: >> I highly doubt "phonon:amd64" with a dependency on "phonon-backend" will >> work with "phonon-backend-vlc:armel" which provides "phonon-backend". >> >> If phonon-backend would be a normal pack

Re: architecture-specific dependencies on virtual packages

2012-07-13 Thread Jonathan Nieder
Hi, David Kalnischkies wrote: > On Mon, Jul 9, 2012 at 2:34 PM, Jonathan Nieder wrote: >> Conflicts with an architecture seem kind of like conflicts with a >> version. That would mean that that virtual packages wouldn't qualify. >> Could that work well in practice? > > Probably hard to implemen

Re: architecture-specific dependencies on virtual packages

2012-07-13 Thread David Kalnischkies
On Mon, Jul 9, 2012 at 2:34 PM, Jonathan Nieder wrote: > David Kalnischkies wrote: >> while playing around with the APT code regarding architecture-specific >> dependencies I stumbled over the handling of Provides in that context: >> >> Package: pkga >> Status: install ok installed >> Architecture

Re: architecture-specific dependencies on virtual packages

2012-07-09 Thread Jonathan Nieder
David Kalnischkies wrote: > while playing around with the APT code regarding architecture-specific > dependencies I stumbled over the handling of Provides in that context: > > Package: pkga > Status: install ok installed > Architecture: i386 > Provides: foo > > Package pkgb > Architecture: amd64 >