![](https://seccdn.libravatar.org/avatar/5ecd2370515d7d1fc6bd26ffeba0e952.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 12.02.2012 19:59, schrieb Wolfgang Rosenauer:
Hi,
(btw, I'm always confused if opensuse-packaging or opensuse-factory is the right list for that kind of questions. Do we really need both?)
Opensuse-Factory is mainly for systemd infights and KDE3 legacy maintainence questions nowadays. I guess you chose the right list ;-)
I'm not deep into PHP app packaging but I'm working on an update for an existing app in server:php:applications right now.
Great. Which?
But I have quite some open questions and even searching on en.opensuse.org or looking at other similar packages didn't shed some light on them.
Is there any kind of packaging guide for PHP apps and Apache configuration policies I haven't found yet?
I've been searching and asking for some but didn't fine much of value. I ended up with following some unwritten conventions and making some decisions on my own. Is it a pear package or a traditional "unzip tarball" app?
The app I'm working on is installing itself into /srv/www/NAME. Others are using /srv/www/htdocs/NAME.
Legacy stuff like horde3 installs itself to /srv/www/htdocs. phpmyadmin adheres to this schema too. If your existing app lives there, stick with it. If the app is currently not shipped with openSUSE and sufficiently modern to separate config from readonly "program" stuff, /usr/share/php5 may be a valid place too. Debian does it this way.
In addition it is patched to have its php config files in /etc instead of the application directory. Do we really want that?
Debian does it this way. If the patches are working, I suggest putting the ro stuff in /usr/share/php5/app and the config stuff in etc.
Do we want to fiddle with the Apache config in %post or similar to add required modules (a2enmod)?
Cannot answer that without looking at it.
Should apps be enabled with their installation or via server flags?
If you ask me, they should only be accessible from localhost by default.
Anyone got a pointer to openSUSE specific packaging guidelines here?
Sorry, no. - -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk84EGcACgkQCs1dsHJ/X7C8PgCgu2xy6xG18tk3SH6Mp9yBovGU Hl4AoN2tw4deMn4B+OsVYB5zabf2NByj =eWcs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org