Gentoo Archives: gentoo-commits

From: "Renat Lumpau (rl03)" <rl03@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/webapps: webapp-eclass.xml
Date: Tue, 04 Dec 2007 00:36:42
Message-Id: E1IzLm9-0003Ke-8D@stork.gentoo.org
1 rl03 07/12/04 00:36:37
2
3 Modified: webapp-eclass.xml
4 Log:
5 Minor revisions, bug #188949
6
7 Revision Changes Path
8 1.13 xml/htdocs/proj/en/webapps/webapp-eclass.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/webapps/webapp-eclass.xml?rev=1.13&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/webapps/webapp-eclass.xml?rev=1.13&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/webapps/webapp-eclass.xml?r1=1.12&r2=1.13
13
14 Index: webapp-eclass.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/webapps/webapp-eclass.xml,v
17 retrieving revision 1.12
18 retrieving revision 1.13
19 diff -u -r1.12 -r1.13
20 --- webapp-eclass.xml 19 Feb 2007 18:58:49 -0000 1.12
21 +++ webapp-eclass.xml 4 Dec 2007 00:36:36 -0000 1.13
22 @@ -1,6 +1,6 @@
23 <?xml version="1.0" encoding="UTF-8"?>
24 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
25 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/webapps/webapp-eclass.xml,v 1.12 2007/02/19 18:58:49 rl03 Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/webapps/webapp-eclass.xml,v 1.13 2007/12/04 00:36:36 rl03 Exp $ -->
27
28 <guide link="/proj/en/webapps/webapp-eclass.xml" lang="en">
29 <title>webapp.eclass Documentation</title>
30 @@ -10,7 +10,7 @@
31 </author>
32
33 <abstract>
34 -The goal of this guide is to teach the reader how to create and maintain ebuilds
35 +The goal of this guide is to show the reader how to create and maintain ebuilds
36 for web applications. It presents an overview of webapp.eclass and then
37 discusses three ebuilds of increasing complexity and functionality.
38 </abstract>
39 @@ -19,8 +19,8 @@
40 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
41 <license/>
42
43 -<version>1.1</version>
44 -<date>2006-07-09</date>
45 +<version>1.2</version>
46 +<date>2007-12-03</date>
47
48 <chapter>
49 <title>Introduction</title>
50 @@ -30,15 +30,15 @@
51
52 <p>
53 <c>webapp.eclass</c> and <c>webapp-config</c> provide a standardized way to
54 -maintain web applications on Gentoo. Server administrators can use the
55 +maintain web applications in Gentoo. Server administrators can use the
56 <c>webapp-config</c> utility to install, upgrade, and remove software.
57 <c>webapp-config</c> relies on a package manager such as Portage to prepare
58 -the application for installation into multiple virtual hosts. On Gentoo, this
59 +the application for installation into multiple virtual hosts. In Gentoo, this
60 is done by an ebuild that uses <c>webapp.eclass</c>.
61 </p>
62
63 <p>
64 -The goal of this guide is to teach the reader how to create and maintain
65 +The goal of this guide is to show the reader how to create and maintain
66 ebuilds for web applications. It presents an overview of
67 <c>webapp.eclass</c> and then discusses three ebuilds of increasing complexity
68 and functionality. Using the <c>webapp-config</c> utility is beyond the scope
69 @@ -62,7 +62,7 @@
70 <c>webapp-config</c> is under active development. Be sure to install the latest
71 version; as of the time of this writing, it is 1.50.14. You can follow the
72 development process on our <uri
73 -link="http://www.vhost-tools.org/">website</uri>.
74 +link="http://sourceforge.net/projects/webapp-config/">website</uri>.
75 </p>
76
77 </body>
78 @@ -83,7 +83,7 @@
79
80 <p>
81 By default, <c>webapp.eclass</c> will be found under
82 -<path>/usr/portage/eclass/</path>. By definition, the source code is the
83 +<path>/usr/portage/eclass/</path>. The source code is the
84 ultimate documentation and should be consulted whenever something does not
85 perform as expected or further clarification is required.
86 </p>
87 @@ -261,9 +261,7 @@
88 Many web-applications written in PHP require that the PHP binary have certain
89 capabilities built-in; common requirements include support for sessions and a
90 specific database engine. This is typically accomplished by using the
91 -<c>depend.php</c> eclass; unfortunately, the author is not aware of any existing
92 -documentation for that eclass. The reader is referred to the eclass itself for
93 -further information and encouraged to consult relevant ebuilds in Portage.
94 +<c>depend.php</c> eclass. Please consult that eclass for further information.
95 </p>
96
97 <warn>
98 @@ -271,19 +269,19 @@
99 ebuilds available. Relying on CPAN is not acceptable.
100 </warn>
101
102 -<p>
103 +<warn>
104 A common mistake with specifying dependencies for web applications is to
105 <c>RDEPEND</c> on a database engine such as MySQL or
106 PostgreSQL. Many, if not all, web applications are able to connect to a remote
107 -database server. Thus, a local database should not be required.
108 -</p>
109 +database server. Thus, the ebuild should never explicitly <c>RDEPEND</c> on a database
110 +such as <path>dev-db/mysql</path> or <path>dev-db/postgresql</path>. Instead,
111 +consider <c>RDEPEND</c>ing on the appropriate language bindings.
112 +</warn>
113
114 <note>
115 -Currently, it is not possible to depend on a generic webserver. Instead, you
116 -must explicitly specify the webserver (e.g., <path>net-www/apache</path>). This
117 -is inconvenient and has been reported in <uri
118 -link="http://bugs.gentoo.org/show_bug.cgi?id=11007">bug #11007</uri>; we hope
119 -that this issue will be resolved soon.
120 +Carefully consider whether the web application needs Apache (<path>www-servers/apache</path>),
121 +or if it can work with a generic webserver. Consider using <path>virtual/httpd-basic</path>,
122 +<path>virtual/httpd-cgi</path>, or <path>virtual/httpd-fastcgi</path> instead.
123 </note>
124
125 <p>
126
127
128
129 --
130 gentoo-commits@g.o mailing list