ruby port version going backwards? epoch

Matthias Andree matthias.andree at
Sun Apr 8 09:02:29 UTC 2007

Kris Kennaway <kris at> writes:

> This was fixed, but note that pre-commit checks wouldn't have helped:
> the change was made in one file ( but the effects felt in
> others.  In order to catch it we'd have to iterate over the entire
> ports tree, which would delay each commit by a few tens of minutes, or
> a few hours depending on machine load :)

What a pity. 

Anyways, thanks for the quick fix.

Matthias Andree

More information about the freebsd-ports mailing list