How about the following:
Introduce new tokens, called "alpha", "beta" and "pre", with sort ordering
alpha < beta < pre < '' < number.
We then have (taking as example the 2.0 pre Linux kernel series):
1.3.89 < .. < 1.3.99 < 2.0pre1 < 2.0pre2 < .. < 2.0pre17 < 2.0.0
Christian
pgpLm0pksuVtV
On Thursday, April 16, Manoj Srivastava wrote
>
> I shall have to think about how far do we go, and how to limit
> the scope of this document. I do not think we can cover secure
> programming, portable programming, introduction to common softeware
> tools, historic bugs, I/O programming,
On Wednesday, April 15, Joey Hess wrote
> Herbert Xu wrote:
> > I have a question: What if a package has two or more upstream changelog
> > files?
>
> I think you should chose the "best" (newest / most readable / most complete
> / preferred format), and install it as changelog.gz, and install the
On Tuesday, March 03, Dale Scheetz wrote
>
> Format: 1.5
> Date: Sun, 1 Mar 1998 19:02:48 -0500
> Source: glibc
> Binary: timezones libc6 libc6-pic libc6-dbg locales libc6-doc libc6-dev
> Architecture: source i386 all
> Version: 2.0.7pre1-3
Ugh. There really should be something in the Policy Man
On Monday, March 02, Sven Rudolph wrote
>
> Does anyone remember why the policy doesn't require `update-rc.d
> remove' when the package is being removed?
Because the files under /etc/init.d are conffiles... just like other
conffiles, we want to leave them there so that the user can return to his
5 matches
Mail list logo
