> Note that python24 does not (or at least will not, as of MacPorts 1.7.0) use
> /opt/local/Library/Frameworks/Python.framework, or even
> ${prefix}/Library/Frameworks/Python.framework, which is what you probably
> meant. In MacPorts 1.7.0 we have a new variable ${frameworks_dir}, so it
> will go i
On Aug 30, 2008, at 6:14 AM, Caspar Florian Ebeling wrote:
>>> The package wants to put the kexts into /Library/Extensions,
>>> which is
>>> /opt/local/Library/Extensions for us. That violates the mtree. Would
>>> /opt/local/lib/{tap|tun}.kext be an good place to keep them instead?
>>
>> /opt/l
Since this question is about Portfile development, not using
MacPorts, I'll continue this thread only on macports-dev.
On Aug 21, 2008, at 9:39:54 PM, Mike Savory wrote:
> Im trying to get a local portfile to work for py-libdnet and
> python2.5 (to get scapy 2 running (requires Python 2.5)
>
>
>> The package wants to put the kexts into /Library/Extensions, which is
>> /opt/local/Library/Extensions for us. That violates the mtree. Would
>> /opt/local/lib/{tap|tun}.kext be an good place to keep them instead?
>
> /opt/local/Library/Extensions seems fine to me. /opt/local/Library is
> alread
Mike Savory wrote:
>> I tried both just changing yours to have
>>
>> set python.bin ${prefix}/bin/python2.5
>>
>> and to do add in the
>>
>> PortGroup python25 1.0
>>
>> (which I don't really understand)
PortGroup is like an include statement. It pulls in the code from one of
t
