Mercurial > forge

comparison www/developers.in @ 2667:20013d95d948 octave-forge

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Grammar and typos
author adb014
date Thu, 12 Oct 2006 20:26:02 +0000
parents f137fa9f34ec
children 9da47715addc
comparison
equal deleted inserted replaced
2666:6548c639892b 2667:20013d95d948
152 152
153 <h3>Package structure</h3> 153 <h3>Package structure</h3>
154 <p> 154 <p>
155 Octave has evolved into a source repository is octave pacakges rather 155 Octave has evolved into a source repository is octave pacakges rather
156 than a package in itself. Each sub-directory is considered to be a 156 than a package in itself. Each sub-directory is considered to be a
157 package can should respect Octave's package managers file layout. 157 package and should respect Octave's package managers file layout.
158 <dl> 158 <dl>
159 <dt>package/NOINSTALL 159 <dt>package/NOINSTALL
160 <dd> This is an optional file, whose presence tells octave-forge 160 <dd> This is an optional file, whose presence tells octave-forge
161 that this package should be ignored. This is typically for 161 that this package should be ignored. This is typically for
162 packages that are kept for historical reasons. 162 packages that are kept for historical reasons.
179 179
180 <td>A one line description of the package</td></tr> 180 <td>A one line description of the package</td></tr>
181 <tr><td>Description:</td> 181 <tr><td>Description:</td>
182 <td>A one paragraph description of the package</td></tr> 182 <td>A one paragraph description of the package</td></tr>
183 <tr><td>Categories:</td> 183 <tr><td>Categories:</td>
184 <td>Optional keywords descriping the package 184 <td>Optional keyword describing the package
185 (if no INDEX file is given this is mandatory)</td></tr> 185 (if no INDEX file is given this is mandatory)</td></tr>
186 <tr><td>Problems:</td> 186 <tr><td>Problems:</td>
187 187
188 <td>Optional list of known problems</td></tr> 188 <td>Optional list of known problems</td></tr>
189 <tr><td>Url:</td> 189 <tr><td>Url:</td>
204 <td>An optional short description of the used license 204 <td>An optional short description of the used license
205 (e.g. GPL version 2 or newer). This is optional 205 (e.g. GPL version 2 or newer). This is optional
206 since the file COPYING is mandatory.</td></tr> 206 since the file COPYING is mandatory.</td></tr>
207 <tr><td>SystemRequirements:</td> 207 <tr><td>SystemRequirements:</td>
208 <td>These are the external install dependencies of the package 208 <td>These are the external install dependencies of the package
209 and are not checked by the package manager. This here as a 209 and are not checked by the package manager. This is here as a
210 hint to the distribution packager. They follows the same 210 hint to the distribution packager. They follows the same
211 conventions as the Depends keyword.</td></tr> 211 conventions as the Depends keyword.</td></tr>
212 <tr><td>BuildRequires:</td> 212 <tr><td>BuildRequires:</td>
213 <td>These are the external build dependencies of the package 213 <td>These are the external build dependencies of the package
214 and are not checked by the package manager. This here as 214 and are not checked by the package manager. This is here as
215 a hint to the distribution packager. They follows the same 215 a hint to the distribution packager. They follows the same
216 conventions as the Depends keyword. Note that in 216 conventions as the Depends keyword. Note that in
217 general, packaging systems such as rpm or deb and 217 general, packaging systems such as rpm or deb and
218 autoprobe the install dependencies from the build 218 autoprobe the install dependencies from the build
219 dependencies, and therefore the often a BuildRequires 219 dependencies, and therefore the often a BuildRequires
235 DEBs from the octave packages, and this relies on the 235 DEBs from the octave packages, and this relies on the
236 DESCRIPTION files being correctly formatted. One further 236 DESCRIPTION files being correctly formatted. One further
237 detail to aid the packager is that the SystemRequirments and 237 detail to aid the packager is that the SystemRequirments and
238 BuildRequires keywords can have distribution dependent 238 BuildRequires keywords can have distribution dependent
239 section, and the automatic build process will use these. An 239 section, and the automatic build process will use these. An
240 example pf the format of this is 240 example of the format of this is
241 <pre> 241 <pre>
242 BuildRequires: libtermcap-devel [Mandriva] libtermcap2-devel 242 BuildRequires: libtermcap-devel [Mandriva] libtermcap2-devel
243 </pre> 243 </pre>
244 where the first package name will be used as a default and if 244 where the first package name will be used as a default and if
245 the RPMs are build on a Mandriva distribution, then the second 245 the RPMs are built on a Mandriva distribution, then the second
246 package name will be used instead. 246 package name will be used instead.
247 <dt>package/COPYING 247 <dt>package/COPYING
248 <dd> This is a required containing the license of the package. 248 <dd> This is a required file containing the license of the package.
249 <dt>package/INDEX 249 <dt>package/INDEX
250 <dd> This is an optional file describing the functions provided by 250 <dd> This is an optional file describing the functions provided by
251 the package. If this file is not given then one with be 251 the package. If this file is not given then one with be
252 created automatically from the functions in the package and 252 created automatically from the functions in the package and
253 the Categories keyword. 253 the Categories keyword.