MacPorts_Framework upgrade failes

[dershow]

I have MacPorts_Framework 0.0.1_0 installed, as a dependent to Pallet. I just tried to upgrade outdated (to 0.1.0_0) and I get the following error:

--->  Fetching MacPorts_Framework
--->  Verifying checksum(s) for MacPorts_Framework
--->  Extracting MacPorts_Framework
--->  Configuring MacPorts_Framework
--->  Building MacPorts_Framework
--->  Staging MacPorts_Framework into destroot
Error: Target org.macports.destroot returned: can't read "frameworks_dir": no such variable
Error: Unable to upgrade port: 1

Any idea about the problem?

--Adam

[blb@…]

Hmm, looks like frameworks_dir is like applications_dir and isn't available in 1.6. The normal fix for applications_dir is probably the way to go here as well (eg, ​minivmac port):

# Can be removed once MacPorts 1.7.0 is released
if {![info exists frameworks_dir]} {
    set frameworks_dir /Library/Frameworks
}

Though I don't know if it should be there or ${prefix}/Library/Frameworks.

[armahg@…]

Replying to dersh@alum.mit.edu:

I have MacPorts_Framework 0.0.1_0 installed, as a dependent to Pallet. I just tried to upgrade outdated (to 0.1.0_0) and I get the following error:

--->  Fetching MacPorts_Framework
--->  Verifying checksum(s) for MacPorts_Framework
--->  Extracting MacPorts_Framework
--->  Configuring MacPorts_Framework
--->  Building MacPorts_Framework
--->  Staging MacPorts_Framework into destroot
Error: Target org.macports.destroot returned: can't read "frameworks_dir": no such variable
Error: Unable to upgrade port: 1

Any idea about the problem?

--Adam

I'll correct that shortly. I think its better placed in /Library/Frameworks since thats the place a regular user will search for non-Apple frameworks. Also, its where the current Framework gets installed.

On another note both Pallet and MacPorts.Framework are under development and are not ready for mainstream use yet.

[blb@…]

Replying to armahg@macports.org:

I'll correct that shortly. I think its better placed in /Library/Frameworks since thats the place a regular user will search for non-Apple frameworks. Also, its where the current Framework gets installed.

True, but do note that in 1.7 the applications and framework directories are configurable via macports.conf, and that some things (eg, python) install framework stuff in ${prefix}/Library/Frameworks for better $[prefix} encapsulation.

[blb@…]

armahg@ fixed this in r39472

[(none)]

Milestone Port Bugs deleted