BUG: howl 0.9.10 framework generation

[danchr@…]

During the update to 0.9.10, the howl port was modified to generate a framework. A couple of bugs where introduced:

• The file howl.pc.in was not updated to reflect these changes.
• In line 26 of the Portfile, a directory is moved directly into it's target

destination in the destroot phase.

Of course, these bugs would be relatively simple to fix, but I fail to see the point in the modification in the first place. It significantly alters the behaviour of a package in a way that more or less bypasses the entire build system used by the original port. Other than that, it uses /Library/OpenDarwin, which resides outside ${prefix}, and which AFAICT doesn't have any significant advantages over a location within ${prefix}. It's just yet another directory to delete if people want to uninstall DarwinPorts.

[danchr@…]

Any response to this?

[mww@…]

oops - ok:

-I currently don't have time to fix the pkgconfig files, so backing off from a framework build is ok for me -the fastest way will be, if you just hack the port (howl) according to your needs -optionally - if you like to - take over maintainership (/me has too many ports anyway..)

just one thing: according to porthier(7), e. g. /Library/Frameworks is a perfect place to put stuff

[danchr@…]

(In reply to comment #2)

-I currently don't have time to fix the pkgconfig files, so backing off from a

framework build is ok for

me -the fastest way will be, if you just hack the port (howl) according to your needs -optionally - if you like to - take over maintainership (/me has too many

ports anyway..)

Sure, I'll reverse the changes and assume maintainership of howl.

just one thing: according to porthier(7), e. g. /Library/Frameworks is a

perfect place to put stuff

Indeed it is. IMHO that's a bit inconsistent, but still, you were using /Library/OpenDarwin/Frameworks ;)