/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.52 Revision 1.60
1# Copyright 1999-2009 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.52 2009/03/23 18:41:17 tommy Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.60 2011/08/17 19:28:30 ulm 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 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=4
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 epatch call 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:
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"
87 87
88# 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
89# for details. Usually not needed. 89# for details. Usually not needed.
90#RESTRICT="strip" 90#RESTRICT="strip"
91 91
92
92# Build-time dependencies, such as 93# Build-time dependencies, such as
93# ssl? ( >=dev-libs/openssl-0.9.6b ) 94# ssl? ( >=dev-libs/openssl-0.9.6b )
94# >=dev-lang/perl-5.6.1-r1 95# >=dev-lang/perl-5.6.1-r1
95# 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
96# had installed on your system when you tested the package. Then 97# had installed on your system when you tested the package. Then
107# 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
108# to keep it tidy. 109# to keep it tidy.
109#S="${WORKDIR}/${P}" 110#S="${WORKDIR}/${P}"
110 111
111 112
112# The following src_compile function is implemented as default by portage, so 113# 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# you only need to call it if you need a different behaviour.
115# This function is available only in EAPI 2 and later.
114#src_compile() { 116#src_configure() {
115 # Most open-source packages use GNU autoconf for configuration. 117 # Most open-source packages use GNU autoconf for configuration.
116 # The default, quickest (and preferred) way of running configure is: 118 # The default, quickest (and preferred) way of running configure is:
117 #econf 119 #econf
118 # 120 #
119 # You could use something similar to the following lines to 121 # You could use something similar to the following lines to
124 # process should abort if they aren't successful.) 126 # process should abort if they aren't successful.)
125 #./configure \ 127 #./configure \
126 # --host=${CHOST} \ 128 # --host=${CHOST} \
127 # --prefix=/usr \ 129 # --prefix=/usr \
128 # --infodir=/usr/share/info \ 130 # --infodir=/usr/share/info \
129 # --mandir=/usr/share/man || die "./configure failed" 131 # --mandir=/usr/share/man || die
130 # 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
131 # this package FHS 2.2-compliant. For more information, see 133 # this package FHS 2.2-compliant. For more information, see
132 # http://www.pathname.com/fhs/ 134 # http://www.pathname.com/fhs/
135#}
133 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() {
134 # emake (previously known as pmake) is a script that calls the 143 # emake (previously known as pmake) is a script that calls the
135 # standard GNU make with parallel building options for speedier 144 # standard GNU make with parallel building options for speedier
136 # builds (especially on SMP systems). Try emake first. It might 145 # builds (especially on SMP systems). Try emake first. It might
137 # not work for some packages, because some makefiles have bugs 146 # not work for some packages, because some makefiles have bugs
138 # related to parallelism, in these cases, use emake -j1 to limit 147 # related to parallelism, in these cases, use emake -j1 to limit
139 # 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
140 # that the makefiles have bugs that have been worked around. 149 # that the makefiles have bugs that have been worked around.
141 150
142 #emake || die "emake failed" 151 #emake || die
143#} 152#}
144 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.
145src_install() { 158#src_install() {
146 # You must *personally verify* that this trick doesn't install 159 # You must *personally verify* that this trick doesn't install
147 # anything outside of DESTDIR; do this by reading and 160 # anything outside of DESTDIR; do this by reading and
148 # understanding the install part of the Makefiles. 161 # understanding the install part of the Makefiles.
149 # This is the preferred way to install. 162 # This is the preferred way to install.
150 emake DESTDIR="${D}" install || die "emake install failed" 163 #emake DESTDIR="${D}" install || die
151 164
152 # 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
153 # better to fix the Makefiles to allow proper parallelization. 166 # better to fix the Makefiles to allow proper parallelization.
154 # 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.
155 168
161 #emake \ 174 #emake \
162 # prefix="${D}"/usr \ 175 # prefix="${D}"/usr \
163 # mandir="${D}"/usr/share/man \ 176 # mandir="${D}"/usr/share/man \
164 # infodir="${D}"/usr/share/info \ 177 # infodir="${D}"/usr/share/info \
165 # libdir="${D}"/usr/$(get_libdir) \ 178 # libdir="${D}"/usr/$(get_libdir) \
166 # install || die "emake install failed" 179 # install || die
167 # Again, verify the Makefiles! We don't want anything falling 180 # Again, verify the Makefiles! We don't want anything falling
168 # outside of ${D}. 181 # outside of ${D}.
169 182
170 # The portage shortcut to the above command is simply: 183 # The portage shortcut to the above command is simply:
171 # 184 #
172 #einstall || die "einstall failed" 185 #einstall || die
173} 186#}

Legend:
Removed from v.1.52  
changed lines
  Added in v.1.60

  ViewVC Help
Powered by ViewVC 1.1.20