hi, there!

09 Jan 03 00:58, Pavel Andreew wrote to Max Khon:

 MK>>> The last question is why source-only tarballs that are
 MK>>> distributed from sourceforge have such strange version naming?
 SD>> See huskybse/develop-doc for details.
 SD>> Short description for CVS tags:
 PA>    [...skip..]

 PA>    Comment from current Release Manager (me) :-)
 PA>    My working environment is Debian GNU/Linux, and I'm produce this 
 PA> steps for release:
 PA>    1) get sources from CVS;
 PA>    2) run 'debuild' command for each module - this make set of Debian 
 PA> binary
 PA> and source packages;
 PA>    3) upload packages to sf.net.

 PA>    Because "Husky debian source" == "Husky tarball
source" (upstream 
 PA> code include debian package stuff), I'm don't any convert/rename 
 PA> operations; however
 PA> distribution tarballs have "-1" at the end of it's name - this is 
 PA> debian "revision". Don't pay attention to this :)

can we return to previously used scheme for naming source tarballs?
i.e. having -stable or -release for them instead of debian package revision?

/fjoe

PS btw does debian has its own CVS for packages meta-data so it
will be kept separately and will not affect naming source code releases?

--- Msged/BSD 6.0.1