Case of port names?

Scott Haneda talklists at
Fri Feb 27 15:54:55 PST 2009

Stumped entirely, if I run a clean --dist, I will get a checksum  
mismatch with the port name set to ASSP, if I run the port name set to  
assp, I do not.

name			    assp
categories		    mail
description		    Anti-Spam SMTP Proxy (ASSP) Server
long_description	    tba
platforms		    darwin
master_sites		    sourceforge

use_zip			    yes

checksums                   md5     95191c8a081601a5b80557ad606d867a \
67d9587d78e8c6d2696ff13d5ae323bb513421f1 \

depends_run		    bin:perl:perl5.8
distname		    ASSP_${version}-Install
worksrcdir		    ${distname}/ASSP

set assp_base		    ${prefix}/var/ASSP

# This distribution is just perl files
use_configure		    no

Some side questions, I know about `port contents`, is there a command  
to tell me the base in which the install has happened in, other than  
looking through `port contents`?  I want to cd `port something` and  
get right to where the installed files are.

Maybe it is that I am just testing a lot, but a `port uninstall ASSP`  
does not remove the files in /opt/local/var/ASSP, at least, not all  
the time,  What is the best way to get the distfiles, work, and  
installed files gone, as well as unregister them?

No matter what the name is, I can `port install assp` or `port install  
ASSP`, so case is not mattering in the command phase, is this normal?   
This is probably an OS X thing being case i?


On Feb 26, 2009, at 5:01 AM, Ryan Schmidt wrote:
> On Feb 26, 2009, at 06:40, Scott Haneda wrote:
>> On Feb 26, 2009, at 3:39 AM, Ryan Schmidt wrote:
>>> On Feb 26, 2009, at 03:31, Joshua Root wrote:
>>>> Scott Haneda wrote:
>>>>> Are all port names to be lowercase?
>>>> No.
>>> Use whatever case gives you the greatest pleasure, or rather, best  
>>> matches the project name. There was a problem in MacPorts < 1.7.0  
>>> when the case of the port name did not match the case the user  
>>> typed on the command line. Users usually typed port names in all  
>>> lowercase, so ports that used uppercase letters caused problems  
>>> for those users. But now that MacPorts 1.7.0 has fixed that issue,  
>>> there's no reason not to use uppercase letters. We have 187 ports  
>>> currently using uppercase letters in their names.
>> Then to confirm this is correct, I use assp as the name of my port  
>> and ASSP as the distname?
>> name			ASSP
>> distname                assp
> Here, you're showing ASSP as the name of the port and assp as the  
> distname.
>> That did not seem to work for me, I had:
>> name			ASSP
>> version
>> distname		ASSP_${version}-Install
>> This would yield a bad download for me, it could not locate it. The  
>> download URL from sourceforge that works is:
>> Where does ports get the first 'assp' in lowercase in that url?
> That means you're downloading from the sourceforge fetch group? It  
> by default uses the port name as the sourceforge project name, if  
> you specify just:
> master_sites sourceforge
> This is equivalent to
> master_sites sourceforge:${name}
> If you want to change it to something else, you can:
> master_sites sourceforge:sfprojectname


* If you contact me off list replace talklists@ with scott@ *

More information about the macports-users mailing list