From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image
Date: Wed, 26 Nov 2008 21:09:45 +0100 [thread overview]
Message-ID: <ggkae9$170$1@ger.gmane.org> (raw)
In-Reply-To: <1227726026.23391.245.camel@lenovo.internal.reciva.com>
On 26-11-08 20:00, Phil Blundell wrote:
> On Wed, 2008-11-26 at 19:40 +0100, Koen Kooi wrote:
>> if fso-foo has
>>
>> Conflicts: foo
>> Replaces: foo
>>
>> but not
>>
>> Provides: foo
>>
>> opkg will always pick fso-foo when it's present in deploy, while you
>> want an image with foo.
>
> Are you sure that your package fso-foo really wants to Conflict: with
> and Replace: foo without also Providing: it?
I'd rather have it only Conflict:, but that places extra burden on the
fso people.
> Although I don't think
> there is any reason why this is inherently illegitimate, it is certainly
> something of a fringe case and my first suspicion would be that this is
> a packaging bug which is just happening to tickle an opkg bug and/or
> misfeature. I suspect opkg is taking a slightly harder line on this,
> deciding that lack of Provides: in this case must certainly be a
> packaging error, and proceeding as if that Provides: was present. It's
> debatable whether this is a desirable thing for it to be doing but,
> irrespective of that, at least a part of the right answer is probably to
> fix the offending packages.
I have literally no clue about opkg internals, sorry.
regards,
Koen
next prev parent reply other threads:[~2008-11-26 20:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 14:51 preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image Koen Kooi
2008-11-26 16:55 ` Michael 'Mickey' Lauer
2008-11-26 17:28 ` Koen Kooi
2008-11-26 17:40 ` Phil Blundell
2008-11-26 17:49 ` Koen Kooi
2008-11-26 18:03 ` Phil Blundell
2008-11-26 18:40 ` Koen Kooi
2008-11-26 19:00 ` Phil Blundell
2008-11-26 20:09 ` Koen Kooi [this message]
2008-11-26 21:27 ` Phil Blundell
2008-11-27 7:34 ` Koen Kooi
2008-11-26 18:12 ` Sergey Lapin
2008-11-26 18:24 ` Denys Dmytriyenko
2008-11-26 18:33 ` Koen Kooi
2008-11-26 18:45 ` Denys Dmytriyenko
2008-11-26 18:35 ` Phil Blundell
2008-11-28 9:40 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ggkae9$170$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox