PORTVERSION when there is no upstream version number
Matthew Seaman
m.seaman at infracaninophile.co.uk
Tue Oct 21 14:33:31 UTC 2014
On 10/21/14 14:45, Manuel Wiesinger wrote:
> Hi,
>
> what is the best practice for setting PORTVERSION, when the upstream
> port has no version number? Is it fine to go with the date like 20141021?
>
Using the date in this sort of case is a pretty good idea, but you
should prefix it by '0.0.'. The porter's handbook says:
"The idea is to make it easier to sort ports by looking at the version
string. In particular, make sure version number components are always
delimited by a period, and if the date is part of the string, use the
0.0.yyyy.mm.dd format, not dd.mm.yyyy or the non-Y2K compliant yy.mm.dd
format. It is important to prefix the version with 0.0. in case a
release with an actual version number is made, which would be
numerically less than yyyy."
> I'm trying to port postscreen-stats, which is just a collection of small
> scripts without any version numbering.
> See: https://github.com/jvehent/Postscreen-Stats
However, since you're porting something distributed via Github see the
specific instructions here:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#5.4.2.1
Cheers,
Matthew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20141021/9f2c7dd1/attachment.sig>
More information about the freebsd-ports
mailing list