/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.38 Revision 1.50
1# Copyright 1999-2006 Gentoo Foundation 1# Copyright 1999-2008 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.38 2006/06/23 15:50:35 genstef Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.50 2008/03/14 02:22:02 betelgeuse 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# 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
13 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 $(get_libdir) mentioned below wont work
17# without the following line: 25# without the following line:
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
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="" 99DEPEND=""
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
102src_compile() { 111src_compile() {
103 # Most open-source packages use GNU autoconf for configuration. 112 # Most open-source packages use GNU autoconf for configuration.
104 # The quickest (and preferred) way of running configure is: 113 # The quickest (and preferred) way of running configure is:
105 econf || die "econf failed" 114 econf || die "econf failed"
132src_install() { 141src_install() {
133 # You must *personally verify* that this trick doesn't install 142 # You must *personally verify* that this trick doesn't install
134 # anything outside of DESTDIR; do this by reading and 143 # anything outside of DESTDIR; do this by reading and
135 # understanding the install part of the Makefiles. 144 # understanding the install part of the Makefiles.
136 # This is the preferred way to install. 145 # This is the preferred way to install.
137 emake DESTDIR=${D} install || die "emake install failed" 146 emake DESTDIR="${D}" install || die "emake install failed"
138 147
139 # When you hit a failure with emake, do not just use make. It is 148 # When you hit a failure with emake, do not just use make. It is
140 # better to fix the Makefiles to allow proper parallelization. 149 # better to fix the Makefiles to allow proper parallelization.
141 # If you fail with that, use "emake -j1", it's still better than make. 150 # If you fail with that, use "emake -j1", it's still better than make.
142 151
144 # prefix is often an alternative. However if you do this, then 153 # prefix is often an alternative. However if you do this, then
145 # you also need to specify mandir and infodir, since they were 154 # you also need to specify mandir and infodir, since they were
146 # passed to ./configure as absolute paths (overriding the prefix 155 # passed to ./configure as absolute paths (overriding the prefix
147 # setting). 156 # setting).
148 #emake \ 157 #emake \
149 # prefix=${D}/usr \ 158 # prefix="${D}"/usr \
150 # mandir=${D}/usr/share/man \ 159 # mandir="${D}"/usr/share/man \
151 # infodir=${D}/usr/share/info \ 160 # infodir="${D}"/usr/share/info \
152 # libdir=${D}/usr/$(get_libdir) \ 161 # libdir="${D}"/usr/$(get_libdir) \
153 # install || die "emake install failed" 162 # install || die "emake install failed"
154 # Again, verify the Makefiles! We don't want anything falling 163 # Again, verify the Makefiles! We don't want anything falling
155 # outside of ${D}. 164 # outside of ${D}.
156 165
157 # The portage shortcut to the above command is simply: 166 # The portage shortcut to the above command is simply:

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

  ViewVC Help
Powered by ViewVC 1.1.20