[Webapps-common-discuss] webapps-common/doc Webapps-Policy-Manual-DRAFT.sgml,1.12,1.13
seanius@haydn.debian.org
seanius@haydn.debian.org
Update of /cvsroot/webapps-common/webapps-common/doc
In directory haydn:/org/alioth.debian.org/chroot/home/users/seanius/tmp/cvs-serv15539
Modified Files:
Webapps-Policy-Manual-DRAFT.sgml
Log Message:
still working my way down...
Index: Webapps-Policy-Manual-DRAFT.sgml
===================================================================
RCS file: /cvsroot/webapps-common/webapps-common/doc/Webapps-Policy-Manual-DRAFT.sgml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- Webapps-Policy-Manual-DRAFT.sgml 6 Jul 2005 01:09:18 -0000 1.12
+++ Webapps-Policy-Manual-DRAFT.sgml 6 Jul 2005 01:24:58 -0000 1.13
@@ -312,16 +312,34 @@
more information.
<sect id="issues-archindep">Architecture independent scripts (Perl, PHP and others)
- <p><em> FIXME
-
-Where to put them ?
-
-/usr/share/$package ?
-</em>
- <sect id="issues-archdep">Architecture dependant scripts
- <p><em> FIXME
+ <p>Scripts that shouldn't normally need
+ to exist in the standard system path should
+ follow the standard Debian policy and exist
+ in <tt>/usr/share/<var>PACKAGE</var>.
+ <p>However, web applications have the additional
+ requirement that if such scripts are not
+ intended to be directly accessed via the
+ web, they must not exist under the document
+ root or other directly web-accessible
+ location. Scripts intended for execution or
+ interpretation via the web must exist in
+ locations where their underlying source code
+ can be directly retrieved.
- Is /usr/lib/cgi-bin still valid?
+ <sect id="issues-archdep">Architecture dependant binaries
+ <p>The policy for Architecture dependant binaries
+ should follow the general rules of the
+ FHS and Debian policy, and exist in
+ <tt>/usr/lib/<var>PACKAGE</var></tt>.
+ Additionally, policy
+ permits these files to exist in
+ <tt>/usr/lib/cgi-bin/<var>PACKAGE</var></tt>
+ though this may
+ become deprecated in the future.
+ <p>Similar to Architecture-independent files,
+ if such files are intended to be executed via
+ the web, they must not exist in a location
+ where they can be directly retrieved.
</em>
<chapt id="libs">Libraries for web applications
<sect id="libs-phplibs">PHP libraries issues