[40784] trunk/dports/devel/distract/Portfile

[Ryan Schmidt]

On Oct 14, 2008, at 18:54, Thomas Keller wrote:

> Ryan Schmidt schrieb:
>
>> On Oct 14, 2008, at 17:38, tommyd at macports.org wrote:
>>
>>> Revision: 40784
>>>           http://trac.macports.org/changeset/40784
>>> Author:   tommyd at macports.org
>>> Date:     2008-10-14 15:38:14 -0700 (Tue, 14 Oct 2008)
>>> Log Message:
>>> -----------
>>> * distract: make the port's name lowercase so it matches the  
>>> directory
>>> and makes port lint happy
>>>
>>> Modified Paths:
>>> --------------
>>>     trunk/dports/devel/distract/Portfile
>>>
>>> Modified: trunk/dports/devel/distract/Portfile
>>> ===================================================================
>>> --- trunk/dports/devel/distract/Portfile    2008-10-14 22:27:30 UTC
>>> (rev 40783)
>>> +++ trunk/dports/devel/distract/Portfile    2008-10-14 22:38:14 UTC
>>> (rev 40784)
>>> @@ -2,7 +2,7 @@
>>>
>>>  PortSystem 1.0
>>>
>>> -name        DisTract
>>> +name        distract
>>>  version        0.2.5
>>>  categories    devel
>>>  maintainers    tommyd
>>
>> Have you tested what happens if a user has "DisTract" installed  
>> and then
>> you update the port to a new version when it's called "distract"  
>> and the
>> user needs to upgrade? Does "port outdated" consider "DisTract" and
>> "distract" to be the same thing -- does it properly suggest the new
>> version? Does the upgrade work properly?
>
> Hrm... I raised the version number temporarily to the non-existant
> version 0.2.6, rebuilded my local port index and it seems as if port
> outdated does not pick this up.

I suspected this might happen, though perhaps as JMR says it will  
work with MacPorts trunk.

> I've seen "set canonicalname" in a couple of haskell-related ports -
> could this be used to set "distract" and leave name intact while  
> making
> port lint happy?

I don't think that will help. port lint is just telling you the name  
of the port (its ${name} variable) and the name of the directory the  
Portfile is in should match, including case.


>> Probably when the port name and directory name do not match, it's  
>> better
>> to change the directory name rather than the port name. Perhaps  
>> the lint
>> message should be changed to suggest that.
>
> I've ask on IRC and it was suggested that the port name is changed,
> because it would have made problems on case insensitive file systems
> (since only the case changed).

Blah. That's true, that can be a problem too. I'm not sure how rsync  
handles it. I think those using a Subversion working copy it might  
need to do something special to update:

http://subversion.tigris.org/faq.html#case-change


> Alternatively I could probably remove this port altogether, since the
> author stated in a personal email a couple of months ago, that he  
> has no
> more time nor interest continueing the project. Are there any  
> guidelines
> when ports should be removed?

If the software is still useful to you or others, we can keep it,  
even if it's not being updated. Unfortunately we gather no statistics  
on how many people use which ports.

Once the port no longer works with newer OS versions and it cannot be  
fixed, then it might be time to think about removing it.