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

Re: Version specific packages


How about this approach:

Packages including the executables (and whatever else is needed) are
called gri-<version>_<version> (i.e. exactly your current scheme).  These
*are* uploaded to debian.

The package gri-support_<version> contains the other stuff, currently in
your unversioned package, *except* that it doesn't provide any executable
at all.

Then, arrange it such that there are no conflicts at all between gri-<x>
and gri_support, or between gri-<x> and gri-<y>.

Now, gri-<x> will Depend: on gri-support (possibly with a version
requirement), and Provide: gri-program. (or just gri, maybe).

You can then use the update-alternatives mechanism (read up on it) to make
sure that a plain invocation to 'gri' will always catch the latest version
installed, whereas a specific invocation of gri-x will catch a particular

Under these rules, all the 'gri' could be in the normal dist (in the same
way that we have many libgtk* at the moment).

Of course, we'd hope that this is a (relatively) temporary situation, and
that eventually gri will standardise its interface.


|  Jelibean aka  | jules@jellybean.co.uk         |  6 Evelyn Rd	       |
|  Jules aka     | jules@debian.org              |  Richmond, Surrey   |
|  Julian Bean   | jmlb2@hermes.cam.ac.uk        |  TW9 2TF *UK*       |
|  War doesn't demonstrate who's right... just who's left.             |
|  When privacy is outlawed... only the outlaws have privacy.          |

Reply to: