PEAR and static files

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings!

The main remaining issue in PEAR packaging has been placement of  
"static" files. I would like to start handling them by including them  
to the component package and then installing via Role_Web.

However, at least for now I'm having a minor placement issue. I've  
symlinked that static directories from CVS to 'static' of each  
component:

# ln -s /Users/bergie/devel/midcom/fs-midcom/static/ 
midcom.helper.datamanager static

And then regenerated the packages, and made a test install. Now the  
minor issue however is that this "static" gets carried into the  
installation path, meaning that I end up with:

ls /sw/share/midgard/midcom/static/midcom_helper_datamanager/static
communityhtml           htmlarea                tiny_mce
contactchooser_ajax.js  jscript-calendar
datamanager.css         tablerowadder.js

i.e. there is an extra "static" in the path coming from the fact that  
the files are in a "static" dir under the component. I'll continue  
looking for solutions...

/Bergie

Henri Bergius
Consultant Partner, Nemein
henri.bergius-ZpG/[email protected]

Midgard CMS
www.midgard-project.org



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFD9enJNkT8k497k9IRAoGdAJ0cla0z+SXzhWGrSf4mWvbynk/vHQCgujpM
u/ZJVjy7AD5biOPTlvyCYaU=
=+BN9
-----END PGP SIGNATURE-----