Is "MacPort" a valid term?

[Rainer Müller]

markd at macports.org wrote:
>> That's not to say I don't see your point too. "MacPorts port" (and
>> "AppleScript script") is long and sounds silly. Would be neat if we
>> could come up with a new cute term for our ports. Ruby has gems, for
>> instance. What entities could MacPorts have?
> 
> Hmn.  How about "mport" as shorthand for "MacPorts port".  "MacPorts
> mport" would never be used, since it is redundant.

I dislike 'MacPort', but I like the term 'mport'.

'mport' is already used in the source and API as a reference for 
MacPorts (mportinit, mportopen, etc). But this should not stop us from 
using the term as an alternative to 'MacPorts port'.

Rainer