[41852] trunk/dports/games/ctetris

[Ryan Schmidt]

On Nov 11, 2008, at 17:03, nox wrote:

> Le 11 nov. 08 à 22:28, Ryan Schmidt a écrit :
>
>> On Nov 11, 2008, at 09:14, nox wrote:
>>
>>> Le 11 nov. 08 à 12:21, Ryan Schmidt a écrit :
>>>
>>>> On Nov 11, 2008, at 03:14, toby at macports.org wrote:
>>>>
>>>>> Revision: 41852
>>>>>         http://trac.macports.org/changeset/41852
>>>>> Author:   toby at macports.org
>>>>> Date:     2008-11-11 01:14:02 -0800 (Tue, 11 Nov 2008)
>>>>> Log Message:
>>>>> -----------
>>>>> update to 0.42
>>>>
>>>> How will users who had ctetris 0.30 installed learn that the  
>>>> port has changed names to ctris? They won't, unfortunately.  
>>>> Which is why you need to keep a stub ctetris port around which  
>>>> does nothing but inform the user to install ctris instead. See  
>>>> for example the libopensync port which was renamed to opensync:
>>>>
>>>> http://trac.macports.org/changeset/41839
>>>>
>>>> Copy the last version of ctetris back into place using svn copy  
>>>> and the peg revision 41851. Increase the version number so users  
>>>> are informed it's outdated (increasing the version to the  
>>>> current version of ctris seems good). And make it not download  
>>>> or install anything except a readme.
>>>>
>>>>> <snip/>
>>>
>>> Can't we just create some sort of a weekly newsletter with some  
>>> news about MacPorts and in particular renamed/nuked/superseded  
>>> ports?
>>
>> I'm sure only a small portion of MacPorts users are on the  
>> macports-users mailing list. So I don't think that would be helpful.
>
> I'm not talking about a new mailing list or whatever but some kind  
> of a webpage, the URL of it could be added to the output of the  
> selfupdate action.

My friend Kevin has MacPorts installed to get Apache, MySQL and PHP,  
but he doesn't update until I ask him to test something new on his  
machine. If he selfupdates now, it will pull in 6 months worth of new  
ports. How will it show all the ports Kevin has installed which have  
been renamed in the past 6 months?

What if Kevin last selfupdated 6 months ago, but the last time he  
actually tried to upgrade any ports was 12 months ago? How will he  
know which of the ports he has installed have been renamed?

No, I don't want a new web page. I want the existing "port outdated"  
mechanism to handle this. Since MacPorts base has no feature to  
handle port renames, we must currently jump through some hoops in  
ports, keeping a stub port around under the old name to inform users  
to switch to the new name. Improvements to base to help this  
situation are of course welcome!