/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.39 Revision 1.48
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.39 2006/06/25 05:13:00 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.48 2008/03/13 23:05:53 spb 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. See current PMS draft for more details.
16# Eclasses will test for this variable if they need to use EAPI > 0 features.
17# Ebuilds should not define EAPI=1 unless they need to use features added
18# in that version.
19#EAPI=1
13 20
14# inherit lists eclasses to inherit functions from. Almost all ebuilds should 21# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15# inherit eutils, as a large amount of important functionality has been 22# inherit eutils, as a large amount of important functionality has been
16# moved there. For example, the $(get_libdir) mentioned below wont work 23# moved there. For example, the $(get_libdir) mentioned below wont work
17# without the following line: 24# without the following line:
51# Note that normal applications should use SLOT="0" if possible, since 58# Note that normal applications should use SLOT="0" if possible, since
52# there should only be exactly one version installed at a time. 59# 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. 60# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
54SLOT="0" 61SLOT="0"
55 62
56# Using KEYWORDS, we can record masking information *inside* an ebuild 63# Using KEYWORDS, we can record masking information *inside* an ebuild
57# instead of relying on an external package.mask file. Right now, you should 64# 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 65# 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 66# 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 67# 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 ~ 68# /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 69# 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 70# considered unstable until testing proves its stability. So, if you've
64# confirmed that your ebuild works on x86 and ppc, you'd specify: 71# confirmed that your ebuild works on x86 and ppc, you'd specify:
65# KEYWORDS="~x86 ~ppc" 72# KEYWORDS="~x86 ~ppc"
66# Once packages go stable, the ~ prefix is removed. 73# Once packages go stable, the ~ prefix is removed.
67# For binary packages, use -* and then list the archs the bin package 74# 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 75# exists for. If the package was for an x86 binary package, then
69# KEYWORDS would be set like this: KEYWORDS="-* x86" 76# KEYWORDS would be set like this: KEYWORDS="-* x86"
71# compatibility reasons. 78# compatibility reasons.
72KEYWORDS="~x86" 79KEYWORDS="~x86"
73 80
74# Comprehensive list of any and all USE flags leveraged in the ebuild, 81# 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", 82# 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 83# "x86" and "alpha". This is a required variable. If the ebuild doesn't
77# use any USE flags, set to "". 84# use any USE flags, set to "".
78IUSE="gnome X" 85IUSE="gnome X"
79 86
80# 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
81# for details. Usually not needed. 88# for details. Usually not needed.
88# had installed on your system when you tested the package. Then 95# had installed on your system when you tested the package. Then
89# other users hopefully won't be caught without the right version of 96# other users hopefully won't be caught without the right version of
90# a dependency. 97# a dependency.
91DEPEND="" 98DEPEND=""
92 99
93# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 100# Run-time dependencies. Must be defined to whatever this depends on to run.
94#RDEPEND="" 101# The below is valid if the same run-time depends are required to compile.
102RDEPEND="${DEPEND}"
95 103
96# Source directory; the dir where the sources can be found (automatically 104# Source directory; the dir where the sources can be found (automatically
97# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 105# 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 106# If you don't need to change it, leave the S= line out of the ebuild
99# to keep it tidy. 107# to keep it tidy.
100S=${WORKDIR}/${P} 108#S="${WORKDIR}/${P}"
101 109
102src_compile() { 110src_compile() {
103 # Most open-source packages use GNU autoconf for configuration. 111 # Most open-source packages use GNU autoconf for configuration.
104 # The quickest (and preferred) way of running configure is: 112 # The quickest (and preferred) way of running configure is:
105 econf || die "econf failed" 113 econf || die "econf failed"

Legend:
Removed from v.1.39  
changed lines
  Added in v.1.48

  ViewVC Help
Powered by ViewVC 1.1.20