Date: Tue, 15 May 2012 22:18:54 +0400 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Chris Rees <utisoft@gmail.com> Cc: freebsd-ports@freebsd.org, portmgr@freebsd.org Subject: Re: `No strings in PORTVERSION' (non-)limitation Message-ID: <20120515181854.GB15922@hades.panopticon> In-Reply-To: <CADLo838DbT%2BAJbhBVPeVkkFwrhWtXzgFqJqOf9HFQikP5hhx0A@mail.gmail.com> References: <20120515150903.GA15922@hades.panopticon> <CADLo838DbT%2BAJbhBVPeVkkFwrhWtXzgFqJqOf9HFQikP5hhx0A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Chris Rees (utisoft@gmail.com) wrote: > Thanks for following this up; since we discussed this I've been thinking > though- why put the git bit in anyway? Does it have anything special > apart from a date marker, and if not, won't a date suffice? Date doesn't itself indicate that this is a VCS snapshot, it may be upstream versioning scheme as well. `git' otoh is unambigous indication that this is a snapshot, and even tells which VCS it is. This is not limited to VCS snapshots - also alphas/betas/release candidates. Finally, letter-specific version comparison scheme is often needed, so 1.1 < 1.2.git123 or 1.2.beta2 or 1.2.rc2 < 1.2. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120515181854.GB15922>