/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

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

Legend:
Removed from v.1.50  
changed lines
  Added in v.1.68

  ViewVC Help
Powered by ViewVC 1.1.20