/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.22 Revision 1.29
1# Copyright 1999-2003 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.22 2003/07/18 19:54:38 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.29 2004/07/25 08:34:01 mr_bones_ 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
19 19
20# Point to any required sources; these will be automatically downloaded by 20# Point to any required sources; these will be automatically downloaded by
21# Portage. 21# Portage.
22SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 22SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
23 23
24# License of the package. This must match the name of file(s) in 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 25# /usr/portage/licenses/. For complex license combination see the developer
26# docs on gentoo.org for details. 26# docs on gentoo.org for details.
27LICENSE="" 27LICENSE=""
28 28
29# The SLOT variable is used to tell Portage if it's OK to keep multiple 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, 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 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 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, 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. 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 35# emerge clean understands SLOTs, and will keep the most recent version
36# of each SLOT and remove everything else. 36# of each SLOT and remove everything else.
37# Note that normal applications should use SLOT="0" if possible, since 37# Note that normal applications should use SLOT="0" if possible, since
38# there should only be exactly one version installed at a time. 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. 39# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
40SLOT="0" 40SLOT="0"
41 41
42# Using KEYWORDS, we can record masking information *inside* an ebuild 42# Using KEYWORDS, we can record masking information *inside* an ebuild
43# instead of relying on an external package.mask file. Right now, you 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 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. We have 45# the names of all the architectures with which the ebuild works. All of
46# 5 official architecture names right now: "~x86", "~ppc", "~sparc", "~sparc" 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".
47# and "~alpha". The ~ in front of the architecture indicates that the 48# The ~ in front of the architecture indicates that the package is new and
48# package is new and should be considered unstable until testing proves its 49# should be considered unstable until testing proves its stability. Once
49# stability. Once packages go stable the ~ prefix is removed. 50# packages go stable the ~ prefix is removed. So, if you've confirmed that
50# So, if you've confirmed that your ebuild works on x86 and ppc, 51# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
51# you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl 52# For packages that are platform-independent (like Java, PHP or Perl
53# applications) specify all keywords. 53# applications) specify all keywords.
54# For binary packages, use -* and then list the archs the bin package 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 55# exists for. If the package was for an x86 binary package, then
56# KEYWORDS would be set like this: KEYWORDS="-* x86" 56# KEYWORDS would be set like this: KEYWORDS="-* x86"
57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58# compatibility reasons. 58# compatibility reasons.
59KEYWORDS="~x86" 59KEYWORDS="~x86"
60 60
61# Comprehensive list of any and all USE flags leveraged in the ebuild, 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", 62# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
63# "sparc", "x86" and "alpha". This is a required variable. If the 63# "x86" and "alpha". This is a required variable. If the ebuild doesn't
64# ebuild doesn't use any USE flags, set to "". 64# use any USE flags, set to "".
65IUSE="X gnome" 65IUSE="X gnome"
66 66
67# A space delimited list of portage features to restrict. man 5 ebuild
68# for details. Usually not needed.
69#RESTRICT="nostrip"
70
67# Build-time dependencies, such as 71# Build-time dependencies, such as
68# ssl? ( >=openssl-0.9.6b ) 72# ssl? ( >=dev-libs/openssl-0.9.6b )
69# >=perl-5.6.1-r1 73# >=dev-lang/perl-5.6.1-r1
70# It is advisable to use the >= syntax show above, to reflect what you 74# It is advisable to use the >= syntax show above, to reflect what you
71# had installed on your system when you tested the package. Then 75# had installed on your system when you tested the package. Then
72# other users hopefully won't be caught without the right version of 76# other users hopefully won't be caught without the right version of
73# a dependency. 77# a dependency.
74DEPEND="" 78DEPEND=""
75 79
76# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 80# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
77#RDEPEND="" 81#RDEPEND=""
78 82
79# Source directory; the dir where the sources can be found (automatically 83# Source directory; the dir where the sources can be found (automatically
80# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} 84# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
81# if you omit this line. 85# If you don't need to change it, leave the S= line out of the ebuild
86# to keep it tidy.
82S=${WORKDIR}/${P} 87S=${WORKDIR}/${P}
83 88
84src_compile() { 89src_compile() {
85 # Most open-source packages use GNU autoconf for configuration. 90 # Most open-source packages use GNU autoconf for configuration.
86 # You should use something similar to the following lines to 91 # You should use something similar to the following lines to
100 105
101 # Also note that it is cleaner and easier to use econf, which is the 106 # Also note that it is cleaner and easier to use econf, which is the
102 # portage shortcut to the above ./configure statement: 107 # portage shortcut to the above ./configure statement:
103 # 108 #
104 # econf || die 109 # econf || die
105 # Note that econf will die on failure, but plase use econf || die 110 # Note that econf will die on failure, but please use econf || die
106 # for consistency. 111 # for consistency.
107 112
108 # emake (previously known as pmake) is a script that calls the 113 # emake (previously known as pmake) is a script that calls the
109 # standard GNU make with parallel building options for speedier 114 # standard GNU make with parallel building options for speedier
110 # builds (especially on SMP systems). Try emake first. It might 115 # builds (especially on SMP systems). Try emake first. It might
111 # not work for some packages, in which case you'll have to resort 116 # not work for some packages, because some makefiles have bugs
112 # to normal "make". 117 # related to parallelism, in these cases, use emake -j1 to limit
113 emake || die 118 # make to a single process. The -j1 is a visual clue to others
114 #make || die 119 # that the makefiles have bugs that have been worked around.
120 emake || die "emake failed"
115} 121}
116 122
117src_install() { 123src_install() {
118 # You must *personally verify* that this trick doesn't install 124 # You must *personally verify* that this trick doesn't install
119 # anything outside of DESTDIR; do this by reading and 125 # anything outside of DESTDIR; do this by reading and

Legend:
Removed from v.1.22  
changed lines
  Added in v.1.29

  ViewVC Help
Powered by ViewVC 1.1.20