/[gentoo-x86]/skel.ebuild
Gentoo

Contents of /skel.ebuild

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.55 - (hide annotations) (download)
Sat Jan 1 00:01:45 2011 UTC (3 years, 9 months ago) by abcd
Branch: MAIN
Changes since 1.54: +1 -1 lines
Happy New Year 2011!

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

  ViewVC Help
Powered by ViewVC 1.1.20