Neil Bothwick wrote: > > My point is that you are mixing portage and non-portage packages, that's > why portage is getting confused. I don't know much about daemontools, but > it seems the sort of package that should not be in @world, but only > installed as a dependency of something else. > > I'm nit suggesting that you should avoid non-portage packages, that may > be impossible or undesirable, but you should be aware of possible > consequences. When I need portage to install dependencies to a > non-portage package, I generally create a set for them, so you could > create qmail-deps containing both daemontools and openrc and emerge it. > Then you are safe from either being depcleaned. If you ever decide to > stop using qmail, you can just unmerge the set and let portage clean up. > >
I forgot about the sets option. That would be another good way to solve this issue. It does mean emerge/portage doesn't know why the packages are needed but it wouldn't remove them because the user told emerge/portage not too. That may be better than adding daemontools to the world file and much easier than creating a ebuild. Nice thinking Neil. :-D Dale :-) :-)
