/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.37 Revision 1.53
1# Copyright 1999-2006 Gentoo Foundation 1# Copyright 1999-2010 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.37 2006/06/20 17:51:41 genstef Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.53 2010/01/01 00:00:39 abcd 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 13
14# The EAPI variable tells the ebuild format in use.
15# Defaults to 0 if not specified. The current PMS draft contains details on
16# a proposed EAPI=0 definition but is not finalized yet.
17# Eclasses will test for this 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
21
14# inherit lists eclasses to inherit functions from. Almost all ebuilds should 22# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15# inherit eutils, as a large amount of important functionality has been 23# inherit eutils, as a large amount of important functionality has been
16# moved there. For example, the $(get_libdir) mentioned below wont work 24# moved there. For example, the epatch call mentioned below wont work
17# without the following line: 25# without the following line:
18inherit eutils 26inherit eutils
19# A well-used example of an eclass function that needs eutils is epatch. If 27# 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 28# your source needs patches applied, it's suggested to put your patch in the
21# 'files' directory and use: 29# 'files' directory and use:
22# 30#
23# epatch ${FILESDIR}/patch-name-here 31# epatch "${FILESDIR}"/patch-name-here
24# 32#
25# eclasses tend to list descriptions of how to use their functions properly. 33# eclasses tend to list descriptions of how to use their functions properly.
26# take a look at /usr/portage/eclasses/ for more examples. 34# take a look at /usr/portage/eclasses/ for more examples.
27 35
28# Short one-line description of this package. 36# Short one-line description of this package.
51# Note that normal applications should use SLOT="0" if possible, since 59# Note that normal applications should use SLOT="0" if possible, since
52# there should only be exactly one version installed at a time. 60# 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. 61# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
54SLOT="0" 62SLOT="0"
55 63
56# Using KEYWORDS, we can record masking information *inside* an ebuild 64# Using KEYWORDS, we can record masking information *inside* an ebuild
57# 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
58# 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
59# 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
60# architectures can be found in the keywords.desc file which is in 68# architectures can be found in the keywords.desc file which is in
61# /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 ~
62# 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
63# considered unstable until testing proves its stability. So, if you've 71# considered unstable until testing proves its stability. So, if you've
64# 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:
65# KEYWORDS="~x86 ~ppc" 73# KEYWORDS="~x86 ~ppc"
66# Once packages go stable, the ~ prefix is removed. 74# Once packages go stable, the ~ prefix is removed.
67# For binary packages, use -* and then list the archs the bin package 75# For binary packages, use -* and then list the archs the bin package
68# exists for. If the package was for an x86 binary package, then 76# exists for. If the package was for an x86 binary package, then
69# KEYWORDS would be set like this: KEYWORDS="-* x86" 77# KEYWORDS would be set like this: KEYWORDS="-* x86"
71# compatibility reasons. 79# compatibility reasons.
72KEYWORDS="~x86" 80KEYWORDS="~x86"
73 81
74# 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,
75# 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",
76# "x86" and "alpha". This is a required variable. If the ebuild doesn't 84# "x86" and "alpha". This is a required variable. If the ebuild doesn't
77# use any USE flags, set to "". 85# use any USE flags, set to "".
78IUSE="X gnome" 86IUSE="gnome X"
79 87
80# 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
81# for details. Usually not needed. 89# for details. Usually not needed.
82#RESTRICT="strip" 90#RESTRICT="strip"
83 91
86# >=dev-lang/perl-5.6.1-r1 94# >=dev-lang/perl-5.6.1-r1
87# 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
88# had installed on your system when you tested the package. Then 96# had installed on your system when you tested the package. Then
89# 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
90# a dependency. 98# a dependency.
91DEPEND="" 99#DEPEND=""
92 100
93# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 101# Run-time dependencies. Must be defined to whatever this depends on to run.
94#RDEPEND="" 102# The below is valid if the same run-time depends are required to compile.
103RDEPEND="${DEPEND}"
95 104
96# Source directory; the dir where the sources can be found (automatically 105# Source directory; the dir where the sources can be found (automatically
97# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 106# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
98# 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
99# to keep it tidy. 108# to keep it tidy.
100S=${WORKDIR}/${P} 109#S="${WORKDIR}/${P}"
101 110
111
112# The following src_compile function is implemented as default by portage, so
113# you only need to call it, if you need a different behaviour.
102src_compile() { 114#src_compile() {
103 # Most open-source packages use GNU autoconf for configuration. 115 # Most open-source packages use GNU autoconf for configuration.
104 # The quickest (and preferred) way of running configure is: 116 # The default, quickest (and preferred) way of running configure is:
105 econf || die "econf failed" 117 #econf
106 # 118 #
107 # You could use something similar to the following lines to 119 # You could use something similar to the following lines to
108 # configure your package before compilation. The "|| die" portion 120 # configure your package before compilation. The "|| die" portion
109 # at the end will stop the build process if the command fails. 121 # at the end will stop the build process if the command fails.
110 # You should use this at the end of critical commands in the build 122 # You should use this at the end of critical commands in the build
124 # builds (especially on SMP systems). Try emake first. It might 136 # builds (especially on SMP systems). Try emake first. It might
125 # not work for some packages, because some makefiles have bugs 137 # not work for some packages, because some makefiles have bugs
126 # related to parallelism, in these cases, use emake -j1 to limit 138 # related to parallelism, in these cases, use emake -j1 to limit
127 # make to a single process. The -j1 is a visual clue to others 139 # make to a single process. The -j1 is a visual clue to others
128 # that the makefiles have bugs that have been worked around. 140 # that the makefiles have bugs that have been worked around.
141
129 emake || die "emake failed" 142 #emake || die "emake failed"
130} 143#}
131 144
132src_install() { 145src_install() {
133 # You must *personally verify* that this trick doesn't install 146 # You must *personally verify* that this trick doesn't install
134 # anything outside of DESTDIR; do this by reading and 147 # anything outside of DESTDIR; do this by reading and
135 # understanding the install part of the Makefiles. 148 # understanding the install part of the Makefiles.
136 # This is the preferred way to install. 149 # This is the preferred way to install.
137 make DESTDIR=${D} install || die 150 emake DESTDIR="${D}" install || die "emake install failed"
151
152 # When you hit a failure with emake, do not just use make. It is
153 # better to fix the Makefiles to allow proper parallelization.
154 # If you fail with that, use "emake -j1", it's still better than make.
138 155
139 # For Makefiles that don't make proper use of DESTDIR, setting 156 # For Makefiles that don't make proper use of DESTDIR, setting
140 # prefix is often an alternative. However if you do this, then 157 # prefix is often an alternative. However if you do this, then
141 # you also need to specify mandir and infodir, since they were 158 # you also need to specify mandir and infodir, since they were
142 # passed to ./configure as absolute paths (overriding the prefix 159 # passed to ./configure as absolute paths (overriding the prefix
143 # setting). 160 # setting).
144 #make \ 161 #emake \
145 # prefix=${D}/usr \ 162 # prefix="${D}"/usr \
146 # mandir=${D}/usr/share/man \ 163 # mandir="${D}"/usr/share/man \
147 # infodir=${D}/usr/share/info \ 164 # infodir="${D}"/usr/share/info \
148 # libdir=${D}/usr/$(get_libdir) \ 165 # libdir="${D}"/usr/$(get_libdir) \
149 # install || die 166 # install || die "emake install failed"
150 # Again, verify the Makefiles! We don't want anything falling 167 # Again, verify the Makefiles! We don't want anything falling
151 # outside of ${D}. 168 # outside of ${D}.
152 169
153 # The portage shortcut to the above command is simply: 170 # The portage shortcut to the above command is simply:
154 # 171 #
155 #einstall || die 172 #einstall || die "einstall failed"
156} 173}

Legend:
Removed from v.1.37  
changed lines
  Added in v.1.53

  ViewVC Help
Powered by ViewVC 1.1.20