/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.15 Revision 1.30
1# Copyright 1999-2002 Gentoo Technologies, Inc. 1# Copyright 1999-2004 Gentoo Foundation
2# Distributed under the terms of the GNU General Public License v2 2# Distributed under the terms of the GNU General Public License v2
3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.15 2002/10/18 18:52:09 blizzy Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.30 2004/08/24 12:14:06 lv Exp $
4 4
5# NOTE: The comments in this file are for instruction and documentation. 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 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 7# remember to remove them before submitting or committing your ebuild. That
8# doesn't mean you can't add your own comments though. 8# doesn't mean you can't add your own comments though.
9 9
10# The 'Header' on the third line should just be left alone. When your ebuild 10# The 'Header' on the third line should just be left alone. When your ebuild
11# will be commited to cvs, the details on that line will be automatically 11# will be committed to cvs, the details on that line will be automatically
12# generated to contain the correct data. 12# generated to contain the correct data.
13
14# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15# inherit eutils, as a large amount of important functionality has been
16# moved there. For example, the $(get_libdir) mentioned below wont work
17# without the following line:
18inherit eutils
19# A well-used example of an eclass function that needs eutils is epatch. If
20# your source needs patches applied, it's suggested to put your patch in the
21# 'files' directory and use:
22#
23# epatch ${FILESDIR}/patch-name-here
24#
25# eclasses tend to list descriptions of how to use their functions properly.
26# take a look at /usr/portage/eclasses/ for more examples.
13 27
14# Short one-line description of this package. 28# Short one-line description of this package.
15DESCRIPTION="This is a sample skeleton ebuild file" 29DESCRIPTION="This is a sample skeleton ebuild file"
16 30
17# Homepage, not used by Portage directly but handy for developer reference 31# Homepage, not used by Portage directly but handy for developer reference
18HOMEPAGE="http://foo.bar.com" 32HOMEPAGE="http://foo.bar.com/"
19 33
20# Point to any required sources; these will be automatically downloaded by 34# Point to any required sources; these will be automatically downloaded by
21# Portage. 35# Portage.
22SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 36SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
23 37
24# License of the package. This must match the name of file(s) in 38# License of the package. This must match the name of file(s) in
25# /usr/portage/licenses/. For complex license combination see the developer 39# /usr/portage/licenses/. For complex license combination see the developer
26# docs on gentoo.org for details. 40# docs on gentoo.org for details.
27LICENSE="" 41LICENSE=""
28 42
29# The SLOT variable is used to tell Portage if it's OK to keep multiple 43# 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, 44# 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 45# 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 46# 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, 47# 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. 48# 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 49# emerge clean understands SLOTs, and will keep the most recent version
36# of each SLOT and remove everything else. 50# of each SLOT and remove everything else.
37# Note that normal applications should use SLOT="0" if possible, since 51# Note that normal applications should use SLOT="0" if possible, since
38# there should only be exactly one version installed at a time. 52# 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. 53# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
40SLOT="0" 54SLOT="0"
41 55
42# Using KEYWORDS, we can record masking information *inside* an ebuild 56# Using KEYWORDS, we can record masking information *inside* an ebuild
43# instead of relying on an external package.mask file. Right now, you 57# 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 58# should set the KEYWORDS variable for every ebuild so that it contains
45# the names of all the architectures with which the ebuild works. We have 59# the names of all the architectures with which the ebuild works. All of
46# 4 official architecture names right now: "x86", "ppc", "sparc" and 60# the official architectures can be found in the keywords.desc file which
47# "sparc64". So, if you've confirmed that your ebuild works on x86 and ppc, 61# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
48# you'd specify: KEYWORDS="x86 ppc" 62# The ~ in front of the architecture indicates that the package is new and
63# should be considered unstable until testing proves its stability. Once
64# packages go stable the ~ prefix is removed. So, if you've confirmed that
65# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
49# For packages that are platform-independant (like Java, PHP or Perl 66# For packages that are platform-independent (like Java, PHP or Perl
50# applications) specify all keywords. 67# applications) specify all keywords.
68# For binary packages, use -* and then list the archs the bin package
69# exists for. If the package was for an x86 binary package, then
70# KEYWORDS would be set like this: KEYWORDS="-* x86"
51# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 71# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
52# compatibility reasons. 72# compatibility reasons.
53KEYWORDS="x86" 73KEYWORDS="~x86"
54 74
55# Comprehensive list of any and all USE flags leveraged in the ebuild, 75# Comprehensive list of any and all USE flags leveraged in the ebuild,
56# with the exception of any ARCH specific flags, i.e. "ppc", "sparc", 76# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
57# "sparc64", "x86" and "alpha". This is a required variable. If the 77# "x86" and "alpha". This is a required variable. If the ebuild doesn't
58# ebuild doesn't use any USE flags, set to "". 78# use any USE flags, set to "".
59IUSE="X gnome" 79IUSE="X gnome"
60 80
81# A space delimited list of portage features to restrict. man 5 ebuild
82# for details. Usually not needed.
83#RESTRICT="nostrip"
84
61# Build-time dependencies, such as 85# Build-time dependencies, such as
62# ssl? ( >=openssl-0.9.6b ) 86# ssl? ( >=dev-libs/openssl-0.9.6b )
63# >=perl-5.6.1-r1 87# >=dev-lang/perl-5.6.1-r1
64# It is advisable to use the >= syntax show above, to reflect what you 88# It is advisable to use the >= syntax show above, to reflect what you
65# had installed on your system when you tested the package. Then 89# had installed on your system when you tested the package. Then
66# other users hopefully won't be caught without the right version of 90# other users hopefully won't be caught without the right version of
67# a dependency. 91# a dependency.
68DEPEND="" 92DEPEND=""
69 93
70# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 94# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
71#RDEPEND="" 95#RDEPEND=""
72 96
73# Source directory; the dir where the sources can be found (automatically 97# Source directory; the dir where the sources can be found (automatically
74# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} 98# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
75# if you omit this line. 99# If you don't need to change it, leave the S= line out of the ebuild
76 100# to keep it tidy.
77S="${WORKDIR}/${P}" 101S=${WORKDIR}/${P}
78 102
79src_compile() { 103src_compile() {
80 # Most open-source packages use GNU autoconf for configuration. 104 # Most open-source packages use GNU autoconf for configuration.
81 # You should use something similar to the following lines to 105 # You should use something similar to the following lines to
82 # configure your package before compilation. The "|| die" portion 106 # configure your package before compilation. The "|| die" portion
91 --mandir=/usr/share/man || die "./configure failed" 115 --mandir=/usr/share/man || die "./configure failed"
92 # Note the use of --infodir and --mandir, above. This is to make 116 # Note the use of --infodir and --mandir, above. This is to make
93 # this package FHS 2.2-compliant. For more information, see 117 # this package FHS 2.2-compliant. For more information, see
94 # http://www.pathname.com/fhs/ 118 # http://www.pathname.com/fhs/
95 119
120 # Also note that it is cleaner and easier to use econf, which is the
121 # portage shortcut to the above ./configure statement:
122 #
123 # econf || die
124 # Note that econf will die on failure, but please use econf || die
125 # for consistency.
126
96 # emake (previously known as pmake) is a script that calls the 127 # emake (previously known as pmake) is a script that calls the
97 # standard GNU make with parallel building options for speedier 128 # standard GNU make with parallel building options for speedier
98 # builds (especially on SMP systems). Try emake first. It might 129 # builds (especially on SMP systems). Try emake first. It might
99 # not work for some packages, in which case you'll have to resort 130 # not work for some packages, because some makefiles have bugs
100 # to normal "make". 131 # related to parallelism, in these cases, use emake -j1 to limit
101 emake || die 132 # make to a single process. The -j1 is a visual clue to others
102 #make || die 133 # that the makefiles have bugs that have been worked around.
134 emake || die "emake failed"
103} 135}
104 136
105src_install() { 137src_install() {
106 # You must *personally verify* that this trick doesn't install 138 # You must *personally verify* that this trick doesn't install
107 # anything outside of DESTDIR; do this by reading and 139 # anything outside of DESTDIR; do this by reading and
114 # setting). 146 # setting).
115 #make \ 147 #make \
116 # prefix=${D}/usr \ 148 # prefix=${D}/usr \
117 # mandir=${D}/usr/share/man \ 149 # mandir=${D}/usr/share/man \
118 # infodir=${D}/usr/share/info \ 150 # infodir=${D}/usr/share/info \
151 # libdir=${D}/usr/$(get_libdir) \
119 # install || die 152 # install || die
120 # Again, verify the Makefiles! We don't want anything falling 153 # Again, verify the Makefiles! We don't want anything falling
121 # outside of ${D}. 154 # outside of ${D}.
155
156 # The portage shortcut to the above command is simply:
157 #
158 #einstall || die
159 # Note that einstall will die on failure, but please use einstall || die
160 # for consistency.
122} 161}

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.30

  ViewVC Help
Powered by ViewVC 1.1.20