/[gentoo-x86]/Gentoo-HOWTO
Gentoo

Diff of /Gentoo-HOWTO

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.2 Revision 1.3
1Gentoo-HOWTO 1Gentoo-HOWTO
2
2Written by Peter Gavin <pete@gentoo.org> and other members of the 3Written by Peter Gavin <pete@gentoo.org> and other members of the
3Gentoo Team 4Gentoo Team
4 5
5------------------------------------------------------------------------ 6------------------------------------------------------------------------
6 7
157 directory. Patches you create yourself just to get your 158 directory. Patches you create yourself just to get your
158 package to build should be called '${PF}-gentoo.diff'. You 159 package to build should be called '${PF}-gentoo.diff'. You
159 should not compress these diffs, since 1) they should not be big 160 should not compress these diffs, since 1) they should not be big
160 enough to require compressing, and 2) cvs does not play well 161 enough to require compressing, and 2) cvs does not play well
161 with binary files. 162 with binary files.
163
164 Please add a suffix or prefix such as ${PV}-${PR} to the tail
165 of every file you put into the files directory, so that the
166 files used for each individual version of your ebuild scripts
167 are distinguishable from one another, and so that the changes
168 between different revisions are visible.
169
170III. .ebuild Files
171
172 .ebuild files are the basis for the entire portage
173 system. They contain all the information required to build a
174 package, and every installed package requires one of these
175 files. .ebuild files are essentially just bash scripts that
176 contain a few functions and environment variable settings. The
177 ebuild command takes care of the rest of the details, such as
178 merging the package into the filesystem and recording the
179 package into the package database.
180
181 A. Naming .ebuild Files
182
183 .ebuild file names are in four sections.
184
185 The first section is the package name, which should only
186 contain lowercase letters, the digits 0-9, and hyphen ('-')
187 characters.
188
189 The second section is the version of the package, which should
190 normally be the same as the version on the main source
191 tarball. The version is normally made up of 2 or 3 numbers
192 separated by periods, such as 1.2 or 4.5.2, and may have a
193 single letter immidiately following the last digit, e.g., 1.4b
194 or 2.6h. This letter should *not* be used to signify alpha or
195 beta status for the package. There are 3 special suffixes that
196 may be used for these packages: _alpha, _beta, and _pre. Each
197 of these suffixes may be immediately followed my a number,
198 e.g., 'linux-2.4.0_pre10'.
199
200 The third section of the package name is the revision number,
201 which is specified by -r#, where '#' is a number,
202 e.g. 'package-4.5.3-r3'. This revision number is independent of
203 the version of the source tarball, but if you need to make
204 non-trivial changes to your .ebuild file, you should copy the
205 .ebuild file to a new file with the revision number
206 incremented by 1. Initial releases normally have no revision
207 number, e.g. 'package-4.5.3'.
208
209 The fourth section of the .ebuild file name is always the
210 .ebuild extension.
211
212 B. Contents of an .ebuild File
213
214 C. Rules for Writing an .ebuild File
215
216IV. Filesystem Locations
217
218 A. Introduction to the FHS
219
220 B. How to Fit Your Packages into the Filesystem

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

  ViewVC Help
Powered by ViewVC 1.1.20