You are not logged in.
For some odd reason, when running namcap on a kde package, it seems to always want mesa as a dependency. Even running it on an official arch package, like kdepim, for instance, it thinks that the mesa dependency is missing. Anyone know if it could be my system or indeed a bug with namcap itself.
Kritoke
http://counter.li.org/ Registered Linux User #318963 kritoke@jabber.org
Offline
very interesting ...
the only thing i can imagine in kde that is actually needing mesa is running the kde screensavers, but they are not in kdepim (or should not be )
The impossible missions are the only ones which succeed.
Offline
I think maybe someone else show attempt to run namcap on their kdepim package or something similar to see if its just my screwy system being its normal self.
Kritoke
http://counter.li.org/ Registered Linux User #318963 kritoke@jabber.org
Offline
sorry, i forgot to post the thing i found out ..
you are absolute right with your discovery:
[damir@Asteraceae klogoturtle]$ namcap klogoturtle-0.6-1.pkg.tar.gz
klogoturtle E: Dependency detected and not included (mesa)
[damir@Asteraceae klogoturtle]$
klogoturtle is a small funny tool to "turtle" graphics (tell go right, go left and draw a dot where you've been, see http://klogoturtle.sourceforge.net/ for more info ); it do not need mesa at all, but as you say, as it is a kde related package, namcap says mesa is needed
sorry that i do not run over kdepim, but this takes hours to build
The impossible missions are the only ones which succeed.
Offline
Two things:
1. Namcap is only good to run on the system you built the package with. Otherwise it will have trouble finding all of the packages that the binaries are linked to.
2. The current mesa package includes X libraries in it. Most prominently /usr/lib/libGL.so. If a kde package links to any of the X libraries (which I would assume it does...) then you will see something weird there.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
2. The current mesa package includes X libraries in it. Most prominently /usr/lib/libGL.so. If a kde package links to any of the X libraries (which I would assume it does...) then you will see something weird there.
yes, i remember forcing upgrade without thinking :oops: ...
http://bbs.archlinux.org/viewtopic.php? … light=mesa
are /usr/lib/libGL.so et al. mesa or xfree86 ?
or better asked (because now it's both) .--- will these libs be in future in mesa or xfree86?
The impossible missions are the only ones which succeed.
Offline
My money's on xfree86.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
some of the conflicting files come from commercial drivers as well (ie nvidia's drivers)
moral of this story is do not rely on namcap as the authority for depend and package building. it is a very good assistant but is not meant as a replacement for research.
AKA uknowme
I am not your friend
Offline
Yes but the question is who owns libGL? Mesa 5.1-2 no longer conflicts.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline