On Wednesday 01 December 2004 04:07 am, GOTO Masanori wrote: > Hmm... gcc provides c-compiler, so "gcc | c-compiler" may be over > description. I don't know this workaround for only aptitude is fine > or not. Any comments? The problem is that when an apt tool encounters a request to install a pure-virtual package, it picks an arbitrary "real" package that provides the virtual package. So, eg, if you say: Depends: c-compiler and no c-compiler is installed, apt will try to install one of the 10 packages that provides c-compiler. That includes a bunch of gcc versions, tcc, bcc, and altgcc (compiled against libc5). On the other hand, if you say: Depends: gcc | c-compiler and no c-compiler is installed, apt will try to install gcc. If a c-compiler is installed, of course, no action will be taken. In this case, libc6-dev only Recommends c-compiler, so only apt frontends that honor Recommends will be affected. The only "aptitude-specific" thing here is that aptitude honors Recommends and many other apt frontends ignore them. I don't know what dselect does with an ambiguous recommendation like this; I suppose it probably gives the user a huge list of packages and says "pick one to make things consistent". Daniel -- /------------------- Daniel Burrows <dburrows@debian.org> ------------------\ | Will the last person to leave the Universe please | | turn off the lights and close the door? | \------------ Evil Overlord, Inc: http://www.eviloverlord.com --------------/
Attachment:
pgpjLS0W_Afn9.pgp
Description: PGP signature