>>>>> On Wed, 17 Apr 2002 23:25:45 -0600 (MDT), Jason Gunthorpe <[EMAIL >>>>> PROTECTED]> said:
>> To the apt people: Could it be that it sees it's a versioned >> depends and it doesn't notice that a versioned xemacs21-nomule is >> about to be installed and just grabs the first in the list? Jason> Perhaps, it is hard to tell without a status file/etc Jason> This is a really long list of choices, I think you should Jason> probably have a provides instead, that is more appropriate for Jason> this. This troubles me. It really should depend on the packages built at the same time. And that'd break being able to do "apt-get update xemacs21" and have it actually update the packages (rather than just the xemacs21 package which would be fulfilled by an older package), unless I did something ugly like have each xemacs21 program package provide "xemacs-21.4.6-<debianversion>-program" and have the xemacs21 package Depend on that. Or are you saying I should just have each program package "Provides: xemacs21". I can't remember the reason now, but there was/is a good reason to have a meta package. Hrm.... Oh wait. It was the dpkg problem with looped provide depends. Does this bug still exist in dpkg? Jim -- @James LewisMoss <[EMAIL PROTECTED]> | Blessed Be! @ http://jimdres.home.mindspring.com | Linux is kewl! @"Argue for your limitations and sure enough, they're yours." Bach -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
