On Tue, Aug 18, 2009 at 10:55:16PM +0200, Andreas Rottmann wrote: > Abdulaziz Ghuloum <[email protected]> writes: > > > On Aug 18, 2009, at 9:16 PM, Andreas Rottmann wrote: > > > >> I think we might have a use for a two-component (similiar to what > >> Debian has), however. For example, if I take Alex Shinn's irregex > >> package (http://synthcode.com/scheme/irregex/), and make a package of > >> it for the (yet-to-be spec'd and developed) R6RS repository, it's > >> useful to keep the upstream version (0.7.3 in this case), as it makes > >> it more obvious what you get. However, the R6RS packaging itself may > >> evolve for a single upstream version; thus a second component may be > >> added to the version number, leading to 0.7.3-1, 0.7.3-2, and so on. > > > > I was thinking the same. I think we only need a single integer after > > the dash, > > > Yes. (Perhaps we come up with use cases for something more complex > later, but for now, a single integer should definitly suffice). > > > and the "-nnn" part should be optional, right? > > > Yes. We should eventually define some guidelines on when to use it, and > when it can/should be omitted, but I guess that'll become clear in the > course of the ongoing discussion, and later implementation.
For what it's worth, that's pretty close to how the FreeBSD ports system works: upstream versions are the main part, and "port revisions" (i.e., changes to the associated FreeBSD ports makefile/patch-file/etc infrastructure) are marked with a ",nn" suffix. Comma is nice here, because it is not often used as part of up-stream package names, which sometimes *do* include hyphens and trailing digits. Cheers, -- Andrew
