[114806] trunk/dports/lang

Ryan Schmidt ryandesign at macports.org
Sun Dec 15 21:50:26 PST 2013


On Dec 15, 2013, at 14:39, jann at macports.org wrote:

> Revision
> 114806
> Author
> jann at macports.org
> Date
> 2013-12-15 12:39:31 -0800 (Sun, 15 Dec 2013)
> Log Message
> 
> Add new version. Remove old version specific port
> Added Paths
> 
> 	• trunk/dports/lang/eiffelstudio/
> 	• trunk/dports/lang/eiffelstudio/Portfile
> Removed Paths
> 
> 	• trunk/dports/lang/eiffelstudio70/

We would usually want to keep the old port around for awhile (usually a year at least) marked as being replaced_by the new one, thereby getting users who had the old port installed upgraded to the new one. Otherwise users may forever keep the old version installed, believing (since not told otherwise by “port outdated”) that they have the latest version. You can use the “obsolete” portgroup for this, or see the sections about port replacement in the guide or the PortfileRecipes wiki page.

What about the remaining eiffelstudio71, eiffelstudio72, and eiffelstudio73 ports? Do those stay?

> Diff
> 
> Added: trunk/dports/lang/eiffelstudio/Portfile (0 => 114806)
> 
> --- trunk/dports/lang/eiffelstudio/Portfile	                        (rev 0)
> +++ trunk/dports/lang/eiffelstudio/Portfile	2013-12-15 20:39:31 UTC (rev 114806)

Was this new port based on any of the old ports? If so you should usually “svn copy” the old port as the basis for your new port, that way the history (i.e. the information you see by running “svn log” or “svn blame”) is retained.



More information about the macports-dev mailing list