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

Re: RFC: New substvars "Binary-Version" and "Next-Source-Version"



On Tue, Sep 17, 2002 at 03:01:12PM -0500, Adam Heath wrote:
> On Tue, 17 Sep 2002, Simon Richter wrote:
> > Next-Source-Version     The lowest version that the next source upload
> >                         could have (Source-Version plus NMU field
> >                         incremented by one)
> Nope, think this one thru again.

What Adam means is that thanks to things like the ~, there's no way of doing
this.

However, you don't actually *need* this -- it's quite enough to make it:

	Next-Source-Version	The Source-Version with NMU field incremented
				by one

and expect the maintainer (who decided to use N-S-V, after all), and
any NMUers, will have the sense not to completely screw with the versioning
scheme.

Maybe this could be trivially achieved by a standard fragment in a
rules file?

Cheers,
aj

-- 
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.

 ``If you don't do it now, you'll be one year older when you do.''

Attachment: pgpogQLbzTitB.pgp
Description: PGP signature


Reply to: