Ticket #8812 (closed submission: fixed)
NEW: tin-recent port
|Reported by:||vincent-opdarw@…||Owned by:||macports-tickets@…|
I'm proposing the following tin port (Portfile will be attached). To make this clear, I've described the Tin development model and the Portfile update policy as a comment in the Portfile. Here's a copy:
# The Tin development model is based on patchsets, as indicated in # the doc/CHANGES file. There are: # * stable patches, numbered ddd (001, 002, and so on), which are # applied to the current stable branch, and in general, to the # unstable branch too (i.e. when this makes sense); # * unstable patches (new features), numbered Uddd (U001, U002, # and so on), which are applied to the unstable branch only. # At some point, the unstable branch is regarded as stable, making # a new stable release and a new stable branch. Then this branch # gets stable patches as usual (fixes, translation updates...). # A new unstable branch is created (split from the current stable # branch) as soon as the first unstable patch (U001) needs to be # applied.
# Portfile update policy: Follow the development line as shown on # <http://www.tin.org/history.html>, preferring unstable versions # to stable ones when there is a split. # The goal of this tin-recent port (as opposed to tin and tin-devel) # is to have the highest upstream version (regarded as either stable # or unstable), i.e. with the latest features, using a single port, # thus benefiting from some port management features, such as those # provided by "port outdated" and "port upgrade".
- Status changed from new to closed
- Resolution set to fixed