Re: xpm and xpm4.7
> In order to be sure that the old a.out library got removed, xpm4.7 had
> to conflict with xpm. This means that this compat package, which must
> provide plain xpm in order to satisfy dependencies, cannot be
> installed without --force-conflicts.
>
> Now _I_ don't have any problem with this, because I don't use anything
> that needs the a.out version anyway, thus I don't even intend to
> install it other than to test.
>
> What I would like to know is whether the situation as it stands (where
> we're talking about having to wedge in a package that we don't really
> want to encourage people to have anyway) is unacceptable to anyone,
> and, if so, what would she/he rather see done.
For libc4/libc5, I renamed libc to libc4 (but still provide libc) and
added a "CONFLICTS: libc (<<4.6.27-11)" to libc5-dev. I don't know if
this is the best way to do it, but it seems to work.
David
--
David Engel Optical Data Systems, Inc.
david@ods.com 1101 E. Arapaho Road
(214) 234-6400 Richardson, TX 75081
Reply to: