/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.1.1.1 Revision 1.49
1# Copyright 1999-2005 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.1.1.1 2005/11/30 09:36:18 chriswhite Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.49 2008/03/14 01:47:23 solar 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. It is for this
17# reason that using EAPI > 0 should be avoided.
18# Eclasses will test for this variable if they need to use EAPI > 0 features.
19# Ebuilds should not define EAPI > 0 unless they absolutely need to use
20# features added in that version.
21#EAPI=0
13 22
14# inherit lists eclasses to inherit functions from. Almost all ebuilds should 23# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15# inherit eutils, as a large amount of important functionality has been 24# inherit eutils, as a large amount of important functionality has been
16# moved there. For example, the $(get_libdir) mentioned below wont work 25# moved there. For example, the $(get_libdir) mentioned below wont work
17# without the following line: 26# without the following line:
52# there should only be exactly one version installed at a time. 61# 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. 62# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
54SLOT="0" 63SLOT="0"
55 64
56# Using KEYWORDS, we can record masking information *inside* an ebuild 65# Using KEYWORDS, we can record masking information *inside* an ebuild
57# instead of relying on an external package.mask file. Right now, you 66# instead of relying on an external package.mask file. Right now, you should
58# should set the KEYWORDS variable for every ebuild so that it contains 67# set the KEYWORDS variable for every ebuild so that it contains the names of
59# the names of all the architectures with which the ebuild works. All of 68# all the architectures with which the ebuild works. All of the official
60# the official architectures can be found in the keywords.desc file which 69# architectures can be found in the keywords.desc file which is in
61# is in /usr/portage/profiles/. Usually you should just set this to "~x86". 70# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~
62# The ~ in front of the architecture indicates that the package is new and 71# in front of the architecture indicates that the package is new and should be
63# should be considered unstable until testing proves its stability. Once 72# considered unstable until testing proves its stability. So, if you've
64# packages go stable the ~ prefix is removed. So, if you've confirmed that 73# confirmed that your ebuild works on x86 and ppc, you'd specify:
65# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc" 74# KEYWORDS="~x86 ~ppc"
75# Once packages go stable, the ~ prefix is removed.
66# For binary packages, use -* and then list the archs the bin package 76# For binary packages, use -* and then list the archs the bin package
67# exists for. If the package was for an x86 binary package, then 77# exists for. If the package was for an x86 binary package, then
68# KEYWORDS would be set like this: KEYWORDS="-* x86" 78# KEYWORDS would be set like this: KEYWORDS="-* x86"
69# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 79# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
70# compatibility reasons. 80# compatibility reasons.
71KEYWORDS="~x86" 81KEYWORDS="~x86"
72 82
73# Comprehensive list of any and all USE flags leveraged in the ebuild, 83# Comprehensive list of any and all USE flags leveraged in the ebuild,
74# with the exception of any ARCH specific flags, i.e. "ppc", "sparc", 84# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
75# "x86" and "alpha". This is a required variable. If the ebuild doesn't 85# "x86" and "alpha". This is a required variable. If the ebuild doesn't
76# use any USE flags, set to "". 86# use any USE flags, set to "".
77IUSE="X gnome" 87IUSE="gnome X"
78 88
79# A space delimited list of portage features to restrict. man 5 ebuild 89# A space delimited list of portage features to restrict. man 5 ebuild
80# for details. Usually not needed. 90# for details. Usually not needed.
81#RESTRICT="nostrip" 91#RESTRICT="strip"
82 92
83# Build-time dependencies, such as 93# Build-time dependencies, such as
84# ssl? ( >=dev-libs/openssl-0.9.6b ) 94# ssl? ( >=dev-libs/openssl-0.9.6b )
85# >=dev-lang/perl-5.6.1-r1 95# >=dev-lang/perl-5.6.1-r1
86# 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
87# had installed on your system when you tested the package. Then 97# had installed on your system when you tested the package. Then
88# 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
89# a dependency. 99# a dependency.
90DEPEND="" 100DEPEND=""
91 101
92# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 102# Run-time dependencies. Must be defined to whatever this depends on to run.
93#RDEPEND="" 103# The below is valid if the same run-time depends are required to compile.
104RDEPEND="${DEPEND}"
94 105
95# Source directory; the dir where the sources can be found (automatically 106# Source directory; the dir where the sources can be found (automatically
96# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 107# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
97# 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
98# to keep it tidy. 109# to keep it tidy.
99S=${WORKDIR}/${P} 110#S="${WORKDIR}/${P}"
100 111
101src_compile() { 112src_compile() {
102 # Most open-source packages use GNU autoconf for configuration. 113 # Most open-source packages use GNU autoconf for configuration.
103 # The quickest (and preferred) way of running configure is: 114 # The quickest (and preferred) way of running configure is:
104 econf || die "econf failed" 115 econf || die "econf failed"
131src_install() { 142src_install() {
132 # You must *personally verify* that this trick doesn't install 143 # You must *personally verify* that this trick doesn't install
133 # anything outside of DESTDIR; do this by reading and 144 # anything outside of DESTDIR; do this by reading and
134 # understanding the install part of the Makefiles. 145 # understanding the install part of the Makefiles.
135 # This is the preferred way to install. 146 # This is the preferred way to install.
136 make DESTDIR=${D} install || die 147 emake DESTDIR="${D}" install || die "emake install failed"
148
149 # When you hit a failure with emake, do not just use make. It is
150 # better to fix the Makefiles to allow proper parallelization.
151 # If you fail with that, use "emake -j1", it's still better than make.
137 152
138 # For Makefiles that don't make proper use of DESTDIR, setting 153 # For Makefiles that don't make proper use of DESTDIR, setting
139 # prefix is often an alternative. However if you do this, then 154 # prefix is often an alternative. However if you do this, then
140 # you also need to specify mandir and infodir, since they were 155 # you also need to specify mandir and infodir, since they were
141 # passed to ./configure as absolute paths (overriding the prefix 156 # passed to ./configure as absolute paths (overriding the prefix
142 # setting). 157 # setting).
143 #make \ 158 #emake \
144 # prefix=${D}/usr \ 159 # prefix="${D}"/usr \
145 # mandir=${D}/usr/share/man \ 160 # mandir="${D}"/usr/share/man \
146 # infodir=${D}/usr/share/info \ 161 # infodir="${D}"/usr/share/info \
147 # libdir=${D}/usr/$(get_libdir) \ 162 # libdir="${D}"/usr/$(get_libdir) \
148 # install || die 163 # install || die "emake install failed"
149 # Again, verify the Makefiles! We don't want anything falling 164 # Again, verify the Makefiles! We don't want anything falling
150 # outside of ${D}. 165 # outside of ${D}.
151 166
152 # The portage shortcut to the above command is simply: 167 # The portage shortcut to the above command is simply:
153 # 168 #
154 #einstall || die 169 #einstall || die "einstall failed"
155} 170}

Legend:
Removed from v.1.1.1.1  
changed lines
  Added in v.1.49

  ViewVC Help
Powered by ViewVC 1.1.20