UPDATE: tin-devel 1.8.1

[vincent-opdarw@…]

The tin port has been updated to 1.8.1, but not the tin-devel port. Though 1.8.1 is a stable release, the version of tin-devel should always be higher or equal to the one of tin, as users of tin-devel want the latest (stable or unstable) release.

[matt@…]

The latest unstable version of tin is 1.7.10 as advertised on <​http://www.tin.org/> If you want to have a portfile for daily snapshots of tin, you can write a portfile for this (tin's actual portfile is a good place to start).

[vincent-opdarw@…]

I don't want a daily snapshot, but the latest release. I don't understand why you don't want set the tin-devel version to 1.8.1, which is more recent than 1.7.10. This is what Debian does: they took 1.7.10, then 1.8.0, then 1.8.1.

[matt@…]

(In reply to comment #2)

I don't want a daily snapshot, but the latest release. I don't understand why you don't want set the tin-devel version to 1.8.1, which is more recent than 1.7.10. This is what Debian does: they took 1.7.10, then 1.8.0, then 1.8.1.

1.8.1 is the *latest* stable release (which is called tin in darwinports) 1.7.10 is the *latest* unstable release (which is called tin-devel in darwinports)

You can check this by yourself by checking <​http://www.tin.org/> which is... tin's homepage.

[vincent-opdarw@…]

For those who do not follow the darwinports mailing-list, I've started a discussion "About -devel versions". So, I think I'll submit a new port whose goal is to follow the development line as shown on <​http://www.tin.org/history.html> (following the dashes and going to the right side when there is a split). In practice, the current version at some date would be the highest version number, with the conventional total order on t-uples (the first components are the most significant).