[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

xpm4 and versioned dependencies, proposed solution



As many of you know, the recently uploaded non-mantainer versions
of xpm4 changed the names of the libc5-based package from xpm4.7
to xpm4 (Provides: xpm4.7), following the name conventions used by 
Michael A. Dorman for the alpha port (and also in use in the m68k port).

Unluckily, dpkg doesn't use the Provides: field to check for versioned
dependencies, so installing the new xpm4 can't be done without
--force-depends (or --force-depends-version).

To solve that, Riku Voipio has suggested to use the old name for
the xpm libc5-based package, and use xpm4g for the libc6-based only.
So, the packages will be named:

xpm4.7 -> libc5 compatibility xpm library
xpm4.7-altdev -> development files for xpm4.7
xpm4g -> libc6-based xpm library
xpm4g-dev -> development files for xpm4g
xpm-bin -> programs for xpm (built with libc6)

As many others may have downloaded these packages from Incoming, I
would like to know if there are any suggestions or objections to that
solution, before doing it.

	Thanks,
-- 
Enrique Zanardi						   ezanardi@ull.es
Dpto. Fisica Fundamental y Experimental			Univ. de La Laguna



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . Trouble? 
e-mail to templin@bucknell.edu .


Reply to: