/[gentoo-x86]/skel.ebuild
Gentoo

Contents of /skel.ebuild

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.53 - (hide annotations) (download)
Fri Jan 1 00:00:39 2010 UTC (4 years, 7 months ago) by abcd
Branch: MAIN
Changes since 1.52: +1 -1 lines
Happy New Year 2010!

1 abcd 1.53 # Copyright 1999-2010 Gentoo Foundation
2 drobbins 1.6 # Distributed under the terms of the GNU General Public License v2
3 sandymac 1.8 # $Header: $
4 drobbins 1.6
5 betelgeuse 1.42 # NOTE: The comments in this file are for instruction and documentation.
6 drobbins 1.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 msterret 1.21 # will be committed to cvs, the details on that line will be automatically
12 drobbins 1.6 # generated to contain the correct data.
13    
14 spb 1.48 # The EAPI variable tells the ebuild format in use.
15 solar 1.49 # Defaults to 0 if not specified. The current PMS draft contains details on
16 betelgeuse 1.50 # a proposed EAPI=0 definition but is not finalized yet.
17 spb 1.48 # Eclasses will test for this variable if they need to use EAPI > 0 features.
18 betelgeuse 1.50 # Ebuilds should not define EAPI > 0 unless they absolutely need to use
19 solar 1.49 # features added in that version.
20     #EAPI=0
21 spb 1.48
22 lv 1.30 # inherit lists eclasses to inherit functions from. Almost all ebuilds should
23     # inherit eutils, as a large amount of important functionality has been
24 tommy 1.52 # moved there. For example, the epatch call mentioned below wont work
25 lv 1.30 # without the following line:
26     inherit eutils
27     # A well-used example of an eclass function that needs eutils is epatch. If
28     # your source needs patches applied, it's suggested to put your patch in the
29     # 'files' directory and use:
30     #
31 tommy 1.52 # epatch "${FILESDIR}"/patch-name-here
32 lv 1.30 #
33     # eclasses tend to list descriptions of how to use their functions properly.
34     # take a look at /usr/portage/eclasses/ for more examples.
35    
36 gbevin 1.3 # Short one-line description of this package.
37     DESCRIPTION="This is a sample skeleton ebuild file"
38    
39     # Homepage, not used by Portage directly but handy for developer reference
40 vapier 1.16 HOMEPAGE="http://foo.bar.com/"
41 blizzy 1.9
42     # Point to any required sources; these will be automatically downloaded by
43     # Portage.
44     SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
45 sandymac 1.5
46 vapier 1.27 # License of the package. This must match the name of file(s) in
47     # /usr/portage/licenses/. For complex license combination see the developer
48 sandymac 1.5 # docs on gentoo.org for details.
49     LICENSE=""
50 achim 1.1
51 blizzy 1.9 # The SLOT variable is used to tell Portage if it's OK to keep multiple
52 vapier 1.27 # versions of the same package installed at the same time. For example,
53 blizzy 1.9 # if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
54     # with 1.2.2), it would be optimal to instruct Portage to not remove
55 vapier 1.27 # libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
56 blizzy 1.9 # we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
57     # emerge clean understands SLOTs, and will keep the most recent version
58     # of each SLOT and remove everything else.
59     # Note that normal applications should use SLOT="0" if possible, since
60     # there should only be exactly one version installed at a time.
61     # DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
62 blizzy 1.12 SLOT="0"
63 blizzy 1.9
64 betelgeuse 1.42 # Using KEYWORDS, we can record masking information *inside* an ebuild
65     # instead of relying on an external package.mask file. Right now, you should
66     # set the KEYWORDS variable for every ebuild so that it contains the names of
67     # all the architectures with which the ebuild works. All of the official
68     # architectures can be found in the keywords.desc file which is in
69     # /usr/portage/profiles/. Usually you should just set this to "~x86". The ~
70     # in front of the architecture indicates that the package is new and should be
71     # considered unstable until testing proves its stability. So, if you've
72     # confirmed that your ebuild works on x86 and ppc, you'd specify:
73 vapier 1.35 # KEYWORDS="~x86 ~ppc"
74     # Once packages go stable, the ~ prefix is removed.
75 vapier 1.22 # For binary packages, use -* and then list the archs the bin package
76     # exists for. If the package was for an x86 binary package, then
77     # KEYWORDS would be set like this: KEYWORDS="-* x86"
78 vapier 1.27 # DO NOT USE KEYWORDS="*". This is deprecated and only for backward
79 blizzy 1.11 # compatibility reasons.
80 seemant 1.18 KEYWORDS="~x86"
81 blizzy 1.15
82     # Comprehensive list of any and all USE flags leveraged in the ebuild,
83     # with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
84 betelgeuse 1.42 # "x86" and "alpha". This is a required variable. If the ebuild doesn't
85 vapier 1.27 # use any USE flags, set to "".
86 vapier 1.39 IUSE="gnome X"
87 blizzy 1.9
88 mr_bones_ 1.29 # A space delimited list of portage features to restrict. man 5 ebuild
89     # for details. Usually not needed.
90 genstef 1.37 #RESTRICT="strip"
91 mr_bones_ 1.29
92 gbevin 1.3 # Build-time dependencies, such as
93 agriffis 1.24 # ssl? ( >=dev-libs/openssl-0.9.6b )
94     # >=dev-lang/perl-5.6.1-r1
95 gbevin 1.3 # It is advisable to use the >= syntax show above, to reflect what you
96     # had installed on your system when you tested the package. Then
97     # other users hopefully won't be caught without the right version of
98     # a dependency.
99 tommy 1.52 #DEPEND=""
100 gbevin 1.3
101 betelgeuse 1.42 # Run-time dependencies. Must be defined to whatever this depends on to run.
102 cardoe 1.40 # The below is valid if the same run-time depends are required to compile.
103     RDEPEND="${DEPEND}"
104 agenkin 1.7
105     # Source directory; the dir where the sources can be found (automatically
106 mr_bones_ 1.26 # unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
107     # If you don't need to change it, leave the S= line out of the ebuild
108     # to keep it tidy.
109 cardoe 1.40 #S="${WORKDIR}/${P}"
110 achim 1.1
111 tommy 1.52
112     # The following src_compile function is implemented as default by portage, so
113     # you only need to call it, if you need a different behaviour.
114     #src_compile() {
115 gbevin 1.3 # Most open-source packages use GNU autoconf for configuration.
116 tommy 1.52 # The default, quickest (and preferred) way of running configure is:
117     #econf
118 vapier 1.33 #
119     # You could use something similar to the following lines to
120 gbevin 1.3 # configure your package before compilation. The "|| die" portion
121     # at the end will stop the build process if the command fails.
122     # You should use this at the end of critical commands in the build
123     # process. (Hint: Most commands are critical, that is, the build
124     # process should abort if they aren't successful.)
125 vapier 1.33 #./configure \
126     # --host=${CHOST} \
127     # --prefix=/usr \
128     # --infodir=/usr/share/info \
129     # --mandir=/usr/share/man || die "./configure failed"
130 gbevin 1.3 # Note the use of --infodir and --mandir, above. This is to make
131     # this package FHS 2.2-compliant. For more information, see
132     # http://www.pathname.com/fhs/
133 blizzy 1.9
134 gbevin 1.3 # emake (previously known as pmake) is a script that calls the
135     # standard GNU make with parallel building options for speedier
136     # builds (especially on SMP systems). Try emake first. It might
137 mr_bones_ 1.26 # not work for some packages, because some makefiles have bugs
138     # related to parallelism, in these cases, use emake -j1 to limit
139     # make to a single process. The -j1 is a visual clue to others
140     # that the makefiles have bugs that have been worked around.
141 tommy 1.52
142     #emake || die "emake failed"
143     #}
144 achim 1.1
145 vapier 1.13 src_install() {
146 gbevin 1.3 # You must *personally verify* that this trick doesn't install
147     # anything outside of DESTDIR; do this by reading and
148 blizzy 1.9 # understanding the install part of the Makefiles.
149 vapier 1.32 # This is the preferred way to install.
150 vapier 1.39 emake DESTDIR="${D}" install || die "emake install failed"
151 genstef 1.38
152     # When you hit a failure with emake, do not just use make. It is
153     # better to fix the Makefiles to allow proper parallelization.
154     # If you fail with that, use "emake -j1", it's still better than make.
155 vapier 1.32
156 gbevin 1.3 # For Makefiles that don't make proper use of DESTDIR, setting
157     # prefix is often an alternative. However if you do this, then
158     # you also need to specify mandir and infodir, since they were
159     # passed to ./configure as absolute paths (overriding the prefix
160     # setting).
161 genstef 1.38 #emake \
162 vapier 1.39 # prefix="${D}"/usr \
163     # mandir="${D}"/usr/share/man \
164     # infodir="${D}"/usr/share/info \
165     # libdir="${D}"/usr/$(get_libdir) \
166 genstef 1.38 # install || die "emake install failed"
167 gbevin 1.3 # Again, verify the Makefiles! We don't want anything falling
168     # outside of ${D}.
169 seemant 1.17
170     # The portage shortcut to the above command is simply:
171     #
172 genstef 1.38 #einstall || die "einstall failed"
173 achim 1.1 }

  ViewVC Help
Powered by ViewVC 1.1.20