[64769] trunk/dports/devel/alex/

nox nox at macports.org
Tue Mar 16 11:55:33 PDT 2010


I don't think that's a good idea, especially when a lot of ports are renamed. We should have a newsletter or something like that for this kind of announcement.

Furthermore, I don't think any clueless user which might overlook the renaming is using Haskell.

Le 16 mars 2010 à 06:49, Ryan Schmidt a écrit :

> 
> On Mar 15, 2010, at 12:18, gwright at macports.org wrote:
> 
>> Revision: 64769
>>         http://trac.macports.org/changeset/64769
>> Author:   gwright at macports.org
>> Date:     2010-03-15 10:18:40 -0700 (Mon, 15 Mar 2010)
>> Log Message:
>> -----------
>> The alex port is moved to hs-alex.
>> 
>> Removed Paths:
>> -------------
>>   trunk/dports/devel/alex/
> 
> 
> The problem here and with the other port(s?) you renamed is that users who had the old port "alex" installed will never know you renamed it to "hs-alex" and will never get future updates you make to hs-alex. To fix this, keep the port "alex" around and make it a stub port. Make it display an error when users try to install it, and mark it as having been "replaced_by hs-alex" (or "replace_by hs-platform-alex"; I don't quite understand the distinction between these ports). See the port osxvnc for an example of how to do this. The old replaced_by ports should continue to exist until all users can be expected to have upgraded; I recommend this period of time be about one year, since I personally know two users who do not upgrade very often so there are undoubtedly others as well.
> 
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev



More information about the macports-dev mailing list