/[gentoo-x86]/skel.ebuild
Gentoo

Contents of /skel.ebuild

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.29 - (show annotations) (download)
Sun Jul 25 08:34:01 2004 UTC (10 years, 5 months ago) by mr_bones_
Branch: MAIN
Changes since 1.28: +4 -0 lines
mention RESTRICT

1 # Copyright 1999-2004 Gentoo Foundation
2 # Distributed under the terms of the GNU General Public License v2
3 # $Header: $
4
5 # NOTE: The comments in this file are for instruction and documentation.
6 # They're not meant to appear with your final, production ebuild. Please
7 # remember to remove them before submitting or committing your ebuild. That
8 # doesn't mean you can't add your own comments though.
9
10 # The 'Header' on the third line should just be left alone. When your ebuild
11 # will be committed to cvs, the details on that line will be automatically
12 # generated to contain the correct data.
13
14 # Short one-line description of this package.
15 DESCRIPTION="This is a sample skeleton ebuild file"
16
17 # Homepage, not used by Portage directly but handy for developer reference
18 HOMEPAGE="http://foo.bar.com/"
19
20 # Point to any required sources; these will be automatically downloaded by
21 # Portage.
22 SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
23
24 # License of the package. This must match the name of file(s) in
25 # /usr/portage/licenses/. For complex license combination see the developer
26 # docs on gentoo.org for details.
27 LICENSE=""
28
29 # The SLOT variable is used to tell Portage if it's OK to keep multiple
30 # versions of the same package installed at the same time. For example,
31 # if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
32 # with 1.2.2), it would be optimal to instruct Portage to not remove
33 # libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
34 # we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
35 # emerge clean understands SLOTs, and will keep the most recent version
36 # of each SLOT and remove everything else.
37 # Note that normal applications should use SLOT="0" if possible, since
38 # there should only be exactly one version installed at a time.
39 # DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
40 SLOT="0"
41
42 # Using KEYWORDS, we can record masking information *inside* an ebuild
43 # instead of relying on an external package.mask file. Right now, you
44 # should set the KEYWORDS variable for every ebuild so that it contains
45 # the names of all the architectures with which the ebuild works. All of
46 # the official architectures can be found in the keywords.desc file which
47 # is in /usr/portage/profiles/. Usually you should just set this to "~x86".
48 # The ~ in front of the architecture indicates that the package is new and
49 # should be considered unstable until testing proves its stability. Once
50 # packages go stable the ~ prefix is removed. So, if you've confirmed that
51 # your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
52 # For packages that are platform-independent (like Java, PHP or Perl
53 # applications) specify all keywords.
54 # For binary packages, use -* and then list the archs the bin package
55 # exists for. If the package was for an x86 binary package, then
56 # KEYWORDS would be set like this: KEYWORDS="-* x86"
57 # DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58 # compatibility reasons.
59 KEYWORDS="~x86"
60
61 # Comprehensive list of any and all USE flags leveraged in the ebuild,
62 # with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
63 # "x86" and "alpha". This is a required variable. If the ebuild doesn't
64 # use any USE flags, set to "".
65 IUSE="X gnome"
66
67 # A space delimited list of portage features to restrict. man 5 ebuild
68 # for details. Usually not needed.
69 #RESTRICT="nostrip"
70
71 # Build-time dependencies, such as
72 # ssl? ( >=dev-libs/openssl-0.9.6b )
73 # >=dev-lang/perl-5.6.1-r1
74 # It is advisable to use the >= syntax show above, to reflect what you
75 # had installed on your system when you tested the package. Then
76 # other users hopefully won't be caught without the right version of
77 # a dependency.
78 DEPEND=""
79
80 # Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
81 #RDEPEND=""
82
83 # Source directory; the dir where the sources can be found (automatically
84 # unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
85 # If you don't need to change it, leave the S= line out of the ebuild
86 # to keep it tidy.
87 S=${WORKDIR}/${P}
88
89 src_compile() {
90 # Most open-source packages use GNU autoconf for configuration.
91 # You should use something similar to the following lines to
92 # configure your package before compilation. The "|| die" portion
93 # at the end will stop the build process if the command fails.
94 # You should use this at the end of critical commands in the build
95 # process. (Hint: Most commands are critical, that is, the build
96 # process should abort if they aren't successful.)
97 ./configure \
98 --host=${CHOST} \
99 --prefix=/usr \
100 --infodir=/usr/share/info \
101 --mandir=/usr/share/man || die "./configure failed"
102 # Note the use of --infodir and --mandir, above. This is to make
103 # this package FHS 2.2-compliant. For more information, see
104 # http://www.pathname.com/fhs/
105
106 # Also note that it is cleaner and easier to use econf, which is the
107 # portage shortcut to the above ./configure statement:
108 #
109 # econf || die
110 # Note that econf will die on failure, but please use econf || die
111 # for consistency.
112
113 # emake (previously known as pmake) is a script that calls the
114 # standard GNU make with parallel building options for speedier
115 # builds (especially on SMP systems). Try emake first. It might
116 # not work for some packages, because some makefiles have bugs
117 # related to parallelism, in these cases, use emake -j1 to limit
118 # make to a single process. The -j1 is a visual clue to others
119 # that the makefiles have bugs that have been worked around.
120 emake || die "emake failed"
121 }
122
123 src_install() {
124 # You must *personally verify* that this trick doesn't install
125 # anything outside of DESTDIR; do this by reading and
126 # understanding the install part of the Makefiles.
127 make DESTDIR=${D} install || die
128 # For Makefiles that don't make proper use of DESTDIR, setting
129 # prefix is often an alternative. However if you do this, then
130 # you also need to specify mandir and infodir, since they were
131 # passed to ./configure as absolute paths (overriding the prefix
132 # setting).
133 #make \
134 # prefix=${D}/usr \
135 # mandir=${D}/usr/share/man \
136 # infodir=${D}/usr/share/info \
137 # install || die
138 # Again, verify the Makefiles! We don't want anything falling
139 # outside of ${D}.
140
141 # The portage shortcut to the above command is simply:
142 #
143 #einstall || die
144 # Note that einstall will die on failure, but please use einstall || die
145 # for consistency.
146 }

  ViewVC Help
Powered by ViewVC 1.1.20