Do we still want Growl to install its prefpane into /Library/PreferencePanes ?

[Boey Maun Suang]

Hi everyone,

As I've just about gotten a port for Growl 0.7.6 working (had to  
fetch from tagged svn, since the tarball is actually missing an  
entire directory), I just wanted to check whether people were still  
happy for Growl to install its preference pane directly into /Library/ 
PreferencePanes (and GrowlMail directly into /Library/Mail/Bundles),  
or whether you think we should make it into ${prefix}/Library/... and  
symlink.  I feel more comfortable about the latter, personally, but I  
want to make sure that there aren't any issues that I may have  
overlooked.

Incidentally (I apologise for not putting this in a separate email,  
but I'm in a rush), Growl wouldn't build with the -t flag; it appears  
that the Rez command that gets invoked insists on creating temporary  
files in /.vol and fails when it can't:

<snip>

/Developer/Tools/Rez -o /opt/local/var/db/dports/build/ 
_Users_boeyms_src_macports-trunk_dports_aqua_Growl/work/Growl-0.7.6/ 
build/Growl.build/Development/GrowlHelperApp.build/ 
ResourceManagerResources/Objects/GrowlScripting.rsrc -d ... <rest of  
command omitted because it's really long />

### /Developer/Tools/Rez - SysError -5000 during create of "/opt/ 
local/var/db/dports/build/_Users_boeyms_src_macports- 
trunk_dports_aqua_Growl/work/Growl-0.7.6/build/Growl.build/ 
Development/GrowlHelperApp.build/ResourceManagerResources/Objects/ 
GrowlScripting.rsrc".
### /Developer/Tools/Rez - Fatal error trying to open the resource  
file "/opt/local/var/db/dports/build/_Users_boeyms_src_macports- 
trunk_dports_aqua_Growl/work/Growl-0.7.6/build/Growl.build/ 
Development/GrowlHelperApp.build/ResourceManagerResources/Objects/ 
GrowlScripting.rsrc" for writing.
Fatal Error!
### /Developer/Tools/Rez - Fatal Error, can't recover.
### /Developer/Tools/Rez - Since errors occurred, /opt/local/var/db/ 
dports/build/_Users_boeyms_src_macports-trunk_dports_aqua_Growl/work/ 
Growl-0.7.6/build/Growl.build/Development/GrowlHelperApp.build/ 
ResourceManagerResources/Objects/GrowlScripting.rsrc's resource fork  
was not written.
** BUILD FAILED **
make: *** [all] Error 1
Warning: Target build has an undeclared dependency on subversion
Warning: A creation/deletion/modification was attempted outside  
sandbox: /.vol/234881026/10943819/main.applescript
Warning: A creation/deletion/modification was attempted outside  
sandbox: /.vol/ 
234881026/10944508/5C3BB5E0-6B3E-44AC-800F-49C65E3C0729-20650-000007779E 
AE5954
Warning: A creation/deletion/modification was attempted outside  
sandbox: /.vol/234881026/10944508/Growl.framework.dep
Warning: A creation/deletion/modification was attempted outside  
sandbox: /.vol/234881026/10945013/GrowlScripting.rsrc
Warning: A creation/deletion/modification was attempted outside  
sandbox: /System/Library/Caches/com.apple.IntlDataCache.le
Warning: A creation/deletion/modification was attempted outside  
sandbox: /System/Library/Caches/com.apple.IntlDataCache.le
Warning: A creation/deletion/modification was attempted outside  
sandbox: /System/Library/Caches/com.apple.IntlDataCache.le

</snip>

I don't know what tried to write to /System/Library/Caches, but  
suffice it to say that omitting the -t flag enabled it to build with  
no problems.  It'd be nice if we could modify trace mode to allow  
writing to /.vol at least, but I won't mind if people are more  
concerned about that path being written to and not cleaned out.

Kind regards,


Maun Suang

-- 
Boey Maun Suang (Boey is my surname)
Email: boeyms at macports.org