/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.48 Revision 1.59
1# Copyright 1999-2008 Gentoo Foundation 1# Copyright 1999-2011 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.48 2008/03/13 23:05:53 spb Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.59 2011/04/14 15:00:52 ssuominen 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.
… …
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 13
14# The EAPI variable tells the ebuild format in use. 14# The EAPI variable tells the ebuild format in use.
15# Defaults to 0 if not specified. See current PMS draft for more details. 15# Defaults to 0 if not specified.
16# It is suggested that you the latest EAPI approved by the Council.
17# The PMS contains specifications for all EAPIs. Eclasses will test for this
16# Eclasses will test for this variable if they need to use EAPI > 0 features. 18# variable if they need to use EAPI > 0 features.
17# Ebuilds should not define EAPI=1 unless they need to use features added
18# in that version.
19#EAPI=1 19EAPI=4
20 20
21# inherit lists eclasses to inherit functions from. Almost all ebuilds should 21# inherit lists eclasses to inherit functions from. Almost all ebuilds should
22# inherit eutils, as a large amount of important functionality has been 22# inherit eutils, as a large amount of important functionality has been
23# moved there. For example, the $(get_libdir) mentioned below wont work 23# moved there. For example, the epatch call mentioned below wont work
24# without the following line: 24# without the following line:
25inherit eutils 25inherit eutils
26# A well-used example of an eclass function that needs eutils is epatch. If 26# A well-used example of an eclass function that needs eutils is epatch. If
27# your source needs patches applied, it's suggested to put your patch in the 27# your source needs patches applied, it's suggested to put your patch in the
28# 'files' directory and use: 28# 'files' directory and use:
29# 29#
30# epatch ${FILESDIR}/patch-name-here 30# epatch "${FILESDIR}"/patch-name-here
31# 31#
32# eclasses tend to list descriptions of how to use their functions properly. 32# eclasses tend to list descriptions of how to use their functions properly.
33# take a look at /usr/portage/eclasses/ for more examples. 33# take a look at /usr/portage/eclasses/ for more examples.
34 34
35# Short one-line description of this package. 35# Short one-line description of this package.
… …
39HOMEPAGE="http://foo.bar.com/" 39HOMEPAGE="http://foo.bar.com/"
40 40
41# Point to any required sources; these will be automatically downloaded by 41# Point to any required sources; these will be automatically downloaded by
42# Portage. 42# Portage.
43SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 43SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
44
44 45
45# License of the package. This must match the name of file(s) in 46# License of the package. This must match the name of file(s) in
46# /usr/portage/licenses/. For complex license combination see the developer 47# /usr/portage/licenses/. For complex license combination see the developer
47# docs on gentoo.org for details. 48# docs on gentoo.org for details.
48LICENSE="" 49LICENSE=""
… …
62 63
63# Using KEYWORDS, we can record masking information *inside* an ebuild 64# Using KEYWORDS, we can record masking information *inside* an ebuild
64# instead of relying on an external package.mask file. Right now, you should 65# instead of relying on an external package.mask file. Right now, you should
65# set the KEYWORDS variable for every ebuild so that it contains the names of 66# set the KEYWORDS variable for every ebuild so that it contains the names of
66# all the architectures with which the ebuild works. All of the official 67# all the architectures with which the ebuild works. All of the official
67# architectures can be found in the keywords.desc file which is in 68# architectures can be found in the arch.list file which is in
68# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~ 69# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~
69# in front of the architecture indicates that the package is new and should be 70# in front of the architecture indicates that the package is new and should be
70# considered unstable until testing proves its stability. So, if you've 71# considered unstable until testing proves its stability. So, if you've
71# confirmed that your ebuild works on x86 and ppc, you'd specify: 72# confirmed that your ebuild works on x86 and ppc, you'd specify:
72# KEYWORDS="~x86 ~ppc" 73# KEYWORDS="~x86 ~ppc"
… …
86 87
87# A space delimited list of portage features to restrict. man 5 ebuild 88# A space delimited list of portage features to restrict. man 5 ebuild
88# for details. Usually not needed. 89# for details. Usually not needed.
89#RESTRICT="strip" 90#RESTRICT="strip"
90 91
92
91# Build-time dependencies, such as 93# Build-time dependencies, such as
92# ssl? ( >=dev-libs/openssl-0.9.6b ) 94# ssl? ( >=dev-libs/openssl-0.9.6b )
93# >=dev-lang/perl-5.6.1-r1 95# >=dev-lang/perl-5.6.1-r1
94# It is advisable to use the >= syntax show above, to reflect what you 96# It is advisable to use the >= syntax show above, to reflect what you
95# had installed on your system when you tested the package. Then 97# had installed on your system when you tested the package. Then
96# other users hopefully won't be caught without the right version of 98# other users hopefully won't be caught without the right version of
97# a dependency. 99# a dependency.
98DEPEND="" 100#DEPEND=""
99 101
100# Run-time dependencies. Must be defined to whatever this depends on to run. 102# Run-time dependencies. Must be defined to whatever this depends on to run.
101# The below is valid if the same run-time depends are required to compile. 103# The below is valid if the same run-time depends are required to compile.
102RDEPEND="${DEPEND}" 104RDEPEND="${DEPEND}"
103 105
… …
105# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 107# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
106# If you don't need to change it, leave the S= line out of the ebuild 108# If you don't need to change it, leave the S= line out of the ebuild
107# to keep it tidy. 109# to keep it tidy.
108#S="${WORKDIR}/${P}" 110#S="${WORKDIR}/${P}"
109 111
110src_compile() { 112
113# The following src_configure function is implemented as default by portage, so
114# you only need to call it if you need a different behaviour.
115# This function is available only in EAPI 2 and later.
116#src_configure() {
111 # Most open-source packages use GNU autoconf for configuration. 117 # Most open-source packages use GNU autoconf for configuration.
112 # The quickest (and preferred) way of running configure is: 118 # The default, quickest (and preferred) way of running configure is:
113 econf || die "econf failed" 119 #econf
114 # 120 #
115 # You could use something similar to the following lines to 121 # You could use something similar to the following lines to
116 # configure your package before compilation. The "|| die" portion 122 # configure your package before compilation. The "|| die" portion
117 # at the end will stop the build process if the command fails. 123 # at the end will stop the build process if the command fails.
118 # You should use this at the end of critical commands in the build 124 # You should use this at the end of critical commands in the build
… …
120 # process should abort if they aren't successful.) 126 # process should abort if they aren't successful.)
121 #./configure \ 127 #./configure \
122 # --host=${CHOST} \ 128 # --host=${CHOST} \
123 # --prefix=/usr \ 129 # --prefix=/usr \
124 # --infodir=/usr/share/info \ 130 # --infodir=/usr/share/info \
125 # --mandir=/usr/share/man || die "./configure failed" 131 # --mandir=/usr/share/man || die
126 # Note the use of --infodir and --mandir, above. This is to make 132 # Note the use of --infodir and --mandir, above. This is to make
127 # this package FHS 2.2-compliant. For more information, see 133 # this package FHS 2.2-compliant. For more information, see
128 # http://www.pathname.com/fhs/ 134 # http://www.pathname.com/fhs/
135#}
129 136
137# The following src_compile function is implemented as default by portage, so
138# you only need to call it, if you need different behaviour.
139# For EAPI < 2 src_compile runs also commands currently present in
140# src_configure. Thus, if you're using an older EAPI, you need to copy them
141# to your src_compile and drop the src_configure function.
142#src_compile() {
130 # emake (previously known as pmake) is a script that calls the 143 # emake (previously known as pmake) is a script that calls the
131 # standard GNU make with parallel building options for speedier 144 # standard GNU make with parallel building options for speedier
132 # builds (especially on SMP systems). Try emake first. It might 145 # builds (especially on SMP systems). Try emake first. It might
133 # not work for some packages, because some makefiles have bugs 146 # not work for some packages, because some makefiles have bugs
134 # related to parallelism, in these cases, use emake -j1 to limit 147 # related to parallelism, in these cases, use emake -j1 to limit
135 # make to a single process. The -j1 is a visual clue to others 148 # make to a single process. The -j1 is a visual clue to others
136 # that the makefiles have bugs that have been worked around. 149 # that the makefiles have bugs that have been worked around.
137 emake || die "emake failed"
138}
139 150
151 #emake || die
152#}
153
154# The following src_install function is implemented as default by portage, so
155# you only need to call it, if you need different behaviour.
156# For EAPI < 4 src_install is just returing true, so you need to always specify
157# this function in older EAPIs.
140src_install() { 158#src_install() {
141 # You must *personally verify* that this trick doesn't install 159 # You must *personally verify* that this trick doesn't install
142 # anything outside of DESTDIR; do this by reading and 160 # anything outside of DESTDIR; do this by reading and
143 # understanding the install part of the Makefiles. 161 # understanding the install part of the Makefiles.
144 # This is the preferred way to install. 162 # This is the preferred way to install.
145 emake DESTDIR="${D}" install || die "emake install failed" 163 #emake DESTDIR="${D}" install || die
146 164
147 # When you hit a failure with emake, do not just use make. It is 165 # When you hit a failure with emake, do not just use make. It is
148 # better to fix the Makefiles to allow proper parallelization. 166 # better to fix the Makefiles to allow proper parallelization.
149 # If you fail with that, use "emake -j1", it's still better than make. 167 # If you fail with that, use "emake -j1", it's still better than make.
150 168
… …
156 #emake \ 174 #emake \
157 # prefix="${D}"/usr \ 175 # prefix="${D}"/usr \
158 # mandir="${D}"/usr/share/man \ 176 # mandir="${D}"/usr/share/man \
159 # infodir="${D}"/usr/share/info \ 177 # infodir="${D}"/usr/share/info \
160 # libdir="${D}"/usr/$(get_libdir) \ 178 # libdir="${D}"/usr/$(get_libdir) \
161 # install || die "emake install failed" 179 # install || die
162 # Again, verify the Makefiles! We don't want anything falling 180 # Again, verify the Makefiles! We don't want anything falling
163 # outside of ${D}. 181 # outside of ${D}.
164 182
165 # The portage shortcut to the above command is simply: 183 # The portage shortcut to the above command is simply:
166 # 184 #
167 #einstall || die "einstall failed" 185 #einstall || die
168} 186#}
Legend:
Removed from v.1.48  
changed lines
  Added in v.1.59
  ViewVC Help
Powered by ViewVC 1.1.20