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

Re: HOWTO: making a package which compiles fine on slink and potato

Stephane Bortzmeyer wrote:
> A modest HOWTO, which seems to work for me. Comments wlecome 
>      _________________________________________________________________
> Numbering your versions
>    When you build the two packages yourself, pay attention to the version
>    numbering: you typically want the "slink" version to have a lower
>    number, so that future upgrades will do the right thing and install
>    the "potato" version. To do so, I use a numbering scheme which is the
>    one used in [3]NMUs: if my "potato" package is 1.2-5, I call the
>    "slink" package 1.2-4.999. That way, it has an inferior number, and
>    the packages can follow their normal life, being upgraded, without
>    fearing a collision.

I typically use a number number like 1.2-0slink1 for the slink
version of 1.2-1, which leads to packages named like:


Making really obvious that it's built for slink.

Peter Galbraith, research scientist          <GalbraithP@dfo-mpo.gc.ca>
Maurice Lamontagne Institute, Department of Fisheries and Oceans Canada
P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada. 418-775-0852 FAX: 775-0546
    6623'rd GNU/Linux user at the Counter - http://counter.li.org/ 

Reply to: