Re: PHP application packaging policy/best practice?
Kees Leune dijo [Fri, Jan 07, 2005 at 02:19:18PM +0100]:
> I am preparing an ITP for a PHP application that is currently under
> development at my place of employment. While thinking about packaging
> it, I was wondering if there is any PHP application policy or best
> practice. I am now leaning to a setup as follows:
> Note that I chose /usr/lib over /usr/share because according to the
> FHS, /usr/share is meant for "all read-only architecture independent
> data files". Although PHP files are read-only and architecture
> indepedent, I consider them as programs.
Some people have pointed out that other PHP programs go to /usr/share
as well. Just to complement: Perl modules also get installed to
/usr/share if they are not architecture-specific. Python seems not to
be that way, as its standard sys.path does not include /usr/share/*.
Gunnar Wolf - email@example.com - (+52-55)1451-2244 / 5554-9450
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF