/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.1.1.1 Revision 1.26
1# Copyright 1999-2005 Gentoo Foundation 1# Copyright 1999-2004 Gentoo Technologies, Inc.
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.1.1.1 2005/11/30 09:36:18 chriswhite Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.26 2004/03/11 22:38:25 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
11# will be committed 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.
27 13
28# Short one-line description of this package. 14# Short one-line description of this package.
29DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
30 16
31# Homepage, not used by Portage directly but handy for developer reference 17# Homepage, not used by Portage directly but handy for developer reference
33 19
34# Point to any required sources; these will be automatically downloaded by 20# Point to any required sources; these will be automatically downloaded by
35# Portage. 21# Portage.
36SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 22SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
37 23
38# 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
39# /usr/portage/licenses/. For complex license combination see the developer 25# /usr/portage/licenses/. For complex license combination see the developer
40# docs on gentoo.org for details. 26# docs on gentoo.org for details.
41LICENSE="" 27LICENSE=""
42 28
43# 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
44# 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,
45# 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
46# 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
47# 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,
48# 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.
49# emerge clean understands SLOTs, and will keep the most recent version 35# emerge clean understands SLOTs, and will keep the most recent version
50# of each SLOT and remove everything else. 36# of each SLOT and remove everything else.
51# Note that normal applications should use SLOT="0" if possible, since 37# Note that normal applications should use SLOT="0" if possible, since
52# there should only be exactly one version installed at a time. 38# there should only be exactly one version installed at a time.
53# 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.
54SLOT="0" 40SLOT="0"
55 41
56# Using KEYWORDS, we can record masking information *inside* an ebuild 42# Using KEYWORDS, we can record masking information *inside* an ebuild
57# 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
58# 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
59# the names of all the architectures with which the ebuild works. All of 45# the names of all the architectures with which the ebuild works. We have
60# the official architectures can be found in the keywords.desc file which 46# 4 official architecture names right now: "~x86", "~ppc", "~sparc"
61# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
62# The ~ in front of the architecture indicates that the package is new and 47# and "~alpha". The ~ in front of the architecture indicates that the
63# should be considered unstable until testing proves its stability. Once 48# package is new and should be considered unstable until testing proves its
64# packages go stable the ~ prefix is removed. So, if you've confirmed that 49# stability. Once packages go stable the ~ prefix is removed.
65# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc" 50# So, if you've confirmed that your ebuild works on x86 and ppc,
51# you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl
53# applications) specify all keywords.
66# 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
67# 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
68# KEYWORDS would be set like this: KEYWORDS="-* x86" 56# KEYWORDS would be set like this: KEYWORDS="-* x86"
69# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
70# compatibility reasons. 58# compatibility reasons.
71KEYWORDS="~x86" 59KEYWORDS="~x86"
72 60
73# 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,
74# 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",
75# "x86" and "alpha". This is a required variable. If the ebuild doesn't 63# "x86" and "alpha". This is a required variable. If the
76# use any USE flags, set to "". 64# ebuild doesn't use any USE flags, set to "".
77IUSE="X gnome" 65IUSE="X gnome"
78
79# A space delimited list of portage features to restrict. man 5 ebuild
80# for details. Usually not needed.
81#RESTRICT="nostrip"
82 66
83# Build-time dependencies, such as 67# Build-time dependencies, such as
84# ssl? ( >=dev-libs/openssl-0.9.6b ) 68# ssl? ( >=dev-libs/openssl-0.9.6b )
85# >=dev-lang/perl-5.6.1-r1 69# >=dev-lang/perl-5.6.1-r1
86# It is advisable to use the >= syntax show above, to reflect what you 70# It is advisable to use the >= syntax show above, to reflect what you
98# to keep it tidy. 82# to keep it tidy.
99S=${WORKDIR}/${P} 83S=${WORKDIR}/${P}
100 84
101src_compile() { 85src_compile() {
102 # Most open-source packages use GNU autoconf for configuration. 86 # Most open-source packages use GNU autoconf for configuration.
103 # The quickest (and preferred) way of running configure is:
104 econf || die "econf failed"
105 #
106 # You could use something similar to the following lines to 87 # You should use something similar to the following lines to
107 # configure your package before compilation. The "|| die" portion 88 # configure your package before compilation. The "|| die" portion
108 # at the end will stop the build process if the command fails. 89 # at the end will stop the build process if the command fails.
109 # You should use this at the end of critical commands in the build 90 # You should use this at the end of critical commands in the build
110 # process. (Hint: Most commands are critical, that is, the build 91 # process. (Hint: Most commands are critical, that is, the build
111 # process should abort if they aren't successful.) 92 # process should abort if they aren't successful.)
112 #./configure \ 93 ./configure \
113 # --host=${CHOST} \ 94 --host=${CHOST} \
114 # --prefix=/usr \ 95 --prefix=/usr \
115 # --infodir=/usr/share/info \ 96 --infodir=/usr/share/info \
116 # --mandir=/usr/share/man || die "./configure failed" 97 --mandir=/usr/share/man || die "./configure failed"
117 # Note the use of --infodir and --mandir, above. This is to make 98 # Note the use of --infodir and --mandir, above. This is to make
118 # this package FHS 2.2-compliant. For more information, see 99 # this package FHS 2.2-compliant. For more information, see
119 # http://www.pathname.com/fhs/ 100 # http://www.pathname.com/fhs/
101
102 # Also note that it is cleaner and easier to use econf, which is the
103 # portage shortcut to the above ./configure statement:
104 #
105 # econf || die
106 # Note that econf will die on failure, but please use econf || die
107 # for consistency.
120 108
121 # emake (previously known as pmake) is a script that calls the 109 # emake (previously known as pmake) is a script that calls the
122 # standard GNU make with parallel building options for speedier 110 # standard GNU make with parallel building options for speedier
123 # builds (especially on SMP systems). Try emake first. It might 111 # builds (especially on SMP systems). Try emake first. It might
124 # not work for some packages, because some makefiles have bugs 112 # not work for some packages, because some makefiles have bugs
130 118
131src_install() { 119src_install() {
132 # You must *personally verify* that this trick doesn't install 120 # You must *personally verify* that this trick doesn't install
133 # anything outside of DESTDIR; do this by reading and 121 # anything outside of DESTDIR; do this by reading and
134 # understanding the install part of the Makefiles. 122 # understanding the install part of the Makefiles.
135 # This is the preferred way to install.
136 make DESTDIR=${D} install || die 123 make DESTDIR=${D} install || die
137
138 # For Makefiles that don't make proper use of DESTDIR, setting 124 # For Makefiles that don't make proper use of DESTDIR, setting
139 # prefix is often an alternative. However if you do this, then 125 # prefix is often an alternative. However if you do this, then
140 # you also need to specify mandir and infodir, since they were 126 # you also need to specify mandir and infodir, since they were
141 # passed to ./configure as absolute paths (overriding the prefix 127 # passed to ./configure as absolute paths (overriding the prefix
142 # setting). 128 # setting).
143 #make \ 129 #make \
144 # prefix=${D}/usr \ 130 # prefix=${D}/usr \
145 # mandir=${D}/usr/share/man \ 131 # mandir=${D}/usr/share/man \
146 # infodir=${D}/usr/share/info \ 132 # infodir=${D}/usr/share/info \
147 # libdir=${D}/usr/$(get_libdir) \
148 # install || die 133 # install || die
149 # Again, verify the Makefiles! We don't want anything falling 134 # Again, verify the Makefiles! We don't want anything falling
150 # outside of ${D}. 135 # outside of ${D}.
151 136
152 # The portage shortcut to the above command is simply: 137 # The portage shortcut to the above command is simply:
153 # 138 #
154 #einstall || die 139 #einstall || die
140 # Note that einstall will die on failure, but please use einstall || die
141 # for consistency.
155} 142}

Legend:
Removed from v.1.1.1.1  
changed lines
  Added in v.1.26

  ViewVC Help
Powered by ViewVC 1.1.20