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

Thomas Keller tommyd at macports.org
Tue Oct 14 16:54:59 PDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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'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?

> 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).

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?

Thomas.

- --
GPG-Key 0x160D1092 | tommyd3mdi at jabber.ccc.de | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkj1MVMACgkQaf7NlBYNEJIqcQCg/Sw6c9MeXAYLFVNiUkcf63Er
J+QAn3rDgr7ampe+2S0tf57rVlPc+W6b
=gLm5
-----END PGP SIGNATURE-----


More information about the macports-dev mailing list