#13679: UPDATE: tin-devel-1.9.2 ------------------------------------+--------------------------------------- Reporter: darren.bane@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------+--------------------------------------- Changes (by raimue@macports.org): * cc: vinc17@macports.org, raimue@macports.org (added) Comment: We already have tin 1.9.2 as tin-recent. I don't quite get this versioning schema. Why do we have three ports for tin? What is the difference between tin, tin-recent and tin-devel? ''port info tin-recent'' told me to look at http://www.tin.org/history.html, but that does not explain anything for me. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13679#comment:1> MacPorts </projects/macports> Ports system for Mac OS

#13679: UPDATE: tin-devel-1.9.2 ------------------------------------+--------------------------------------- Reporter: darren.bane@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------+--------------------------------------- Comment (by raimue@macports.org): Replying to [comment:2 darren.bane@gmail.com]: Exactly what I think about it. But let us wait for Vincent's comment on this. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13679#comment:3> MacPorts </projects/macports> Ports system for Mac OS

#13679: UPDATE: tin-devel-1.9.2 ------------------------------------+--------------------------------------- Reporter: darren.bane@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------+--------------------------------------- Comment (by vinc17@macports.org): FYI, tin-recent was added following that: [http://trac.macosforge.org/projects/macports/ticket/7335 UPDATE: tin- devel 1.8.1], which had been closed as invalid. Otherwise users would have to switch between tin and tin-devel (which is not possible automatically) to get the latest features and bug fixes. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13679#comment:5> MacPorts </projects/macports> Ports system for Mac OS

#13679: UPDATE: tin-devel-1.9.2 ------------------------------------+--------------------------------------- Reporter: darren.bane@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------+--------------------------------------- Comment (by darren.bane@gmail.com): After skimming both the tin-devel and tin-recent portfiles, I think the latter is better (to be expected since it's the only one that was maintained). My recommendation now is to copy the tin-recent portfile into tin-devel, after adding one last comment saying that the tin-recent portfile should never be edited, instead edit either tin-devel or tin as applicable and copy it to tin-recent. A less palatable alternative is to delete whatever port duplicates tin-recent (tin-devel for now). A port aliasing facility would be nice (i.e. make tin-recent an alias for whatever concrete port), but I don't think this exists. And making tin- devel a depends_run of tin-recent will break "port contents", etc., so I think the current setup is probably for the best. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13679#comment:7> MacPorts </projects/macports> Ports system for Mac OS

#13679: UPDATE: tin-devel-1.9.2 ------------------------------------+--------------------------------------- Reporter: darren.bane@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------+--------------------------------------- Comment (by ryandesign@macports.org): Let's discuss this topic on macports-dev, not in this ticket. "tin-recent" is the only port with "-recent" in its name, so this is nonstandard. Let's discuss on the list how we want to handle this, for all ports. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13679#comment:9> MacPorts </projects/macports> Ports system for Mac OS