On Sat, Jan 10, 2004 at 01:18:04PM +0000, Henning Makholm wrote: > Scripsit "Michael K. Edwards" <mkedebian@sane.net> > > How about a backwards compatibility package, built from the > > lprngtool 1.1.1 source package, that contains the "runtime" > > portions, and some sort of Recommends / Suggests / Replaces magic so > > that dist-upgrade installs both the new lprngtool and the old > > runtime? The Description of the old runtime could say, "If your > > /etc/printcap doesn't reference such-and-such script then it is safe > > to remove this package." > For this to work, the compatibility package needs to inherit the > "lprngtool" name, and the new package must get a new name > (lprngtoolng?). But it's either that, or artificially include the old > script in the new package, or risk things breaking. You could keep the lprngtool name on the official upstream sources, and add a Depends: lprngtool-legacy to pull in the needed extra code. Then a NEWS.Debian entry and a full release cycle ought to be enough to let you drop the dependency for sarge+1, I think. -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature