On Thu, Sep 27, 2007 at 06:39:06PM +0200, Mateusz Jedrasik wrote:

Thursday 27 of September 2007 15:58:42 Alexander Baldeck napisał(a):

...

Pacman should prefer the real pkgname over provides, right?

That would sort of make 'provides' loose its meaning.

Why? By the way, I discussed this a bit with Nagy a while ago. See : http://www.archlinux.org/pipermail/pacman-dev/2007-July/008811.html

Thursday 27 of September 2007 19:02:48 napisałeś(-łaś):

your previous e-mail

Ofcourse, I meant Alexander's e-mail. -- Mateusz Jędrasik tel. +48(51)69-444-90 http://www.neowifi.pl

On Thu, Sep 27, 2007 at 07:02:48PM +0200, Mateusz Jedrasik wrote:

Thursday 27 of September 2007 18:56:37 Xavier napisał(a):

...

Why?

Well if I understand correctly, supposing I have kdemod-kdebase installed, and some package requires kdebase, it will ignore the fact kdemod-kdebase is there and 'provides='kdebase'' and try and install kdebase from whatever other repo.

Unless I'm reading you wrong ;-)

In your case that you mentioned in your previous e-mail (which btw seems like a very chaotic explanation, maybe you can elaborate?) all that's needed to satisfy pacman and not have it pull in fglrx-libs, is to put 'provides=libgl' into libgl-dri.

That would sort it proper.

It seems you are misunderstanding the issue. libgl-dri already provides libgl. But how do you choose between the multiple libgl providers? When you try to install a package requiring libgl, and you don't have libgl installed, nor a package providing it, pacman does the following : - look if a package named libgl is in a repo - if not, it looks for a provider, looking at each repos one by one (in the order defined in pacman.conf), at each packages in a repo one by one (probably in alphabetical order). What this means is that in any case (whether you are a nvidia, intel, whatever, user), pacman will pull fglrx-utils for satisfying the libgl dependency, only because it's the first one it finds. Currently, the user has to first install the correct libgl provider for his hardware (either libgl-dri or fglrx-utils or nvidia-utils), before installing any packages depending on libgl. Otherwise, if the user let pacman install fglrx-utils on his nvidia hardware, bad things might happen. Now, if libgl-dri is renamed to libgl, pacman will choose this package first, which should result in a saner default for everyone.

It seems you are misunderstanding the issue.

libgl-dri already provides libgl. But how do you choose between the multiple libgl providers?

When you try to install a package requiring libgl, and you don't have libgl installed, nor a package providing it, pacman does the following : - look if a package named libgl is in a repo - if not, it looks for a provider, looking at each repos one by one (in the order defined in pacman.conf), at each packages in a repo one by one (probably in alphabetical order).

What this means is that in any case (whether you are a nvidia, intel, whatever, user), pacman will pull fglrx-utils for satisfying the libgl dependency, only because it's the first one it finds.

Currently, the user has to first install the correct libgl provider for his hardware (either libgl-dri or fglrx-utils or nvidia-utils), before installing any packages depending on libgl. Otherwise, if the user let pacman install fglrx-utils on his nvidia hardware, bad things might happen.

Now, if libgl-dri is renamed to libgl, pacman will choose this package first, which should result in a saner default for everyone.

Right. But renaming libgl-dri to libgl is not a real solution neither, but that is much better than current situation. If I have an ATI card, I want to install fglrx-utils. We mentioned some possible solutions here: -let user choose (best solution IMHO, but it may need too many user interactions) -http://www.archlinux.org/pipermail/pacman-dev/2007-July/008816.html -packagers can use many conflicts to force pacman to choose a non-conflicting package (in this example this doesn't help, but in the previous kernel-example, this might help: nvidia-beyond conflicts with vanilla kernel ... (however, these packages shouldn't conflict with each other by the "real" definition of conflicting.)): this won't help yet, see sync402/403. Bye, ngaba ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/

On 10/19/07, Alexander Baldeck wrote:

I renamed libgl-dri to just libgl. fglrx-utils and nvidia-utils still provide libgl but now must be explicitly installed. Then it's all back to the way it used to work. Pacman will just ignore the real libgl package on upgrades.

Erm. I don't know if this is a real question or rhetorical, but I just want to point out that package names are searched for an exact match first, THEN provides, so a package will always be installed BEFORE a provides entry.

On 10/19/07, Xavier wrote:

Also, I don't see anything close to a question there, I think what Alex said was clear :)

Accidentally deleted: On 10/19/07, Alexander Baldeck wrote:

So I ask myself where the problem is? :)