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

Re: splitting xpdf



On Wed, 12 Dec 2001, Michael Bramer wrote:

> On Mon, Dec 10, 2001 at 07:12:29AM -0500, Matt Zimmerman wrote:
> > On Mon, Dec 10, 2001 at 08:39:10PM +1100, Hamish Moffatt wrote:
> >
> > > xpdf -- xpdf, pdftopbm (requires xlibs, freetype, t1 etc)
> > > xpdf-utils -- pdftops, pdfinfo, pdfimages, pdftotext (libpaperg only)
> > >
> > >
> > > Second question: what's the best way to create the packages such
> > > that the binaries don't go missing on existing installations?
> > > Keep an xpdf meta-package depending on two new ones? Or
> > > just live with it?
> >
> > If you want that, while allowing either package to be installed
> > independently, you'll have to rename xpdf above to xpdf-reader or some such,
> > and make xpdf a metapackage that depends on the other two.
> >
> > I wouldn't worry too much about it, except for package dependencies.  As
> > long as there are no programs in Debian which Depend on xpdf that will break
> > unexpectedly if the utils go away, a human can resolve the situation easily.
> > Just mention pdftops, pdfinfo, etc. in the extended description so that they
> > can easily be found.
>
> Please don't break the users systems!

Yes, exactly.  Debian is not just about having a consistent set of
dependencies.  It's about maintaining a system across upgrades.  And, this
change would break users systems, when binaries suddenly went missing.



Reply to: