On 10/7/2018 6:02 PM, Ken Brown wrote:
> I've been experimenting with setup's support for the 'provides:' tag, and
> it's
> not behaving the way I expect [*]. I'm not sure if something in setup's
> interface with libsolv needs to be tweaked or if I'm just misunderstanding
> how
> this should work. Here's what I tried:
>
Shouldn't there be a need for a 'conflicts:' tag as well?
> I created a test repo with packages A, B, and C. I made A require foo (not a
> package), and I made B and C provide foo. The attached script does all this
> [**]. I then ran setup and selected A for installation.
>
So C:foo conflicts with B:foo.
> The result was that libsolv simply chose B for installation, and setup showed
> this in the "Confirm" dialog. What I expected was that libsolv would report
> a
> problem ("A requires foo but no selected or installed packages provide it"),
> with two possible solutions ("Install B or C"). Is that expectation
> unreasonable?
>
Not unreasonable but what happens if B:foo is already installed and
C:foo is the required because the functionality is slightly different?
--
cyg Simple
