ruby port version going backwards? epoch

Matthias Andree matthias.andree at gmx.de
Thu Apr 5 07:58:26 UTC 2007


Greetings,

I just saw this after portsnap fetch update when running pkg_version -IvL=:

ruby-1.8.5.12,1                     >   succeeds index (index has 1.8.6)

Please restore ruby's PORTEPOCH - and consider installing pre-commit check
scripts on the CVS master server that refuse Makefile commits that make
the version go backwards.

-- 
Matthias Andree


More information about the freebsd-ports mailing list