New version of PyGreSQL
swhetzel at gmail.com
Fri Jan 4 18:44:58 UTC 2013
On Thu, Jan 3, 2013 at 12:18 PM, D'Arcy J.M. Cain <darcy at vex.com> wrote:
> On Thu, 03 Jan 2013 21:50:01 +0400
> Ruslan Makhmatkhanov <cvs-src at yandex.ru> wrote:
>> D'Arcy J.M. Cain wrote on 03.01.2013 18:14:
>> > Version 4.1 of PyGreSQL has just been released. I think the
>> > following will update your Makefile:
>> The port was just updated, thank you for heads up. You may point your
>> users here: http://www.freshports.org/databases/py-PyGreSQL for
>> FreeBSD-specific install instructions.
> I see that you call it 4.1,1. Do you always have a PORTEPOCH? I know
> that NetBSD (where I am also a developer) only set the PKGREVISION
> variable when the original commit for a version is modified.
# PORTREVISION - Version of port. Optional. Commonly used to indicate
# that an update has happened that affects the port
# framework itself, but not the distributed software
# (e.g., local patches or Makefile changes).
# PORTEPOCH - Optional. In certain odd cases, the PORTREVISION logic
# can be fooled by ports that appear to go backwards
# numerically (e.g. if port-0.3 is newer than port-1998).
# In this case, incrementing PORTEPOCH forces
# Default: 0 (no effect).
PORTREVISION is the same as PKGREVISION
We use PORTEPOCH as noted in the above comment, or when a port has
gone backwards in revision for some reason. This allows us to do
3.0 < 3.0-1 < 2.9-7,1 < 3.1,1 < 3.0,2
Once PORTEPOCH is added to a port, it can't be removed. As it would
cause the package version to go backwards.
No electrons were maimed while sending this message. Only slightly bruised.
More information about the freebsd-ports