macports guide
Ryan Schmidt
ryandesign at macports.org
Tue Jun 9 17:53:34 PDT 2009
On Jun 9, 2009, at 12:33, Bradley Giesbrecht wrote:
> On Jun 9, 2009, at 9:05 AM, Blair Zajac wrote:
>
>> On Jun 9, 2009, at 8:52 AM, Bradley Giesbrecht wrote:
>>
>>> http://guide.macports.org/chunked/reference.tcl-extensions.html
>>>
>>> Paths seem to not include trailing slashes.
>>>
>>> I thought it was weird that ${destroot} would include a trailing
>>> slash.
>>> ${destroot}${prefix} is shown several times on the above page.
>>
>> That works because ${prefix} begins with a slash and if you had
>> one there then you would have double slashes. ${destroot} doesn't
>> have a trailing slash.
>>
>> But in the following case it looks like it was ${destroot}Library/
>> LaunchDaemons which does need a slash.
>>
>> So I think it's best to only have slashes when you have an
>> absolute path following it.
>
> Thanks for the reply.
>
> This is the type of think I was talking about where dumping ports
> vars to screen would be helpful.
>
> For now I guess I'll just add ui_msg's to all the vars to reveal
> their values.
I do that too sometimes while developing ports. But as you've already
stated, variables that are absolute directory paths do not include a
trailing slash. I believe you can rely on this for all such variables.
More information about the macports-dev
mailing list