/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.28 Revision 1.56
1# Copyright 1999-2004 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.28 2004/06/25 13:29:13 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.56 2011/04/08 01:30:14 vapier 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#EAPI=0
19
20# inherit lists eclasses to inherit functions from. Almost all ebuilds should
21# inherit eutils, as a large amount of important functionality has been
22# moved there. For example, the epatch call mentioned below wont work
23# without the following line:
24inherit eutils
25# A well-used example of an eclass function that needs eutils is epatch. If
26# your source needs patches applied, it's suggested to put your patch in the
27# 'files' directory and use:
28#
29# epatch "${FILESDIR}"/patch-name-here
30#
31# eclasses tend to list descriptions of how to use their functions properly.
32# take a look at /usr/portage/eclasses/ for more examples.
13 33
14# Short one-line description of this package. 34# Short one-line description of this package.
15DESCRIPTION="This is a sample skeleton ebuild file" 35DESCRIPTION="This is a sample skeleton ebuild file"
16 36
17# Homepage, not used by Portage directly but handy for developer reference 37# Homepage, not used by Portage directly but handy for developer reference
38# there should only be exactly one version installed at a time. 58# there should only be exactly one version installed at a time.
39# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package. 59# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
40SLOT="0" 60SLOT="0"
41 61
42# Using KEYWORDS, we can record masking information *inside* an ebuild 62# Using KEYWORDS, we can record masking information *inside* an ebuild
43# instead of relying on an external package.mask file. Right now, you 63# instead of relying on an external package.mask file. Right now, you should
44# should set the KEYWORDS variable for every ebuild so that it contains 64# set the KEYWORDS variable for every ebuild so that it contains the names of
45# the names of all the architectures with which the ebuild works. All of 65# all the architectures with which the ebuild works. All of the official
46# the official architectures can be found in the keywords.desc file which 66# architectures can be found in the arch.list file which is in
47# is in /usr/portage/profiles/. Usually you should just set this to "~x86". 67# /usr/portage/profiles/. Usually you should just set this to "~x86". The ~
48# The ~ in front of the architecture indicates that the package is new and 68# in front of the architecture indicates that the package is new and should be
49# should be considered unstable until testing proves its stability. Once 69# considered unstable until testing proves its stability. So, if you've
50# packages go stable the ~ prefix is removed. So, if you've confirmed that 70# confirmed that your ebuild works on x86 and ppc, you'd specify:
51# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc" 71# KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl 72# Once packages go stable, the ~ prefix is removed.
53# applications) specify all keywords.
54# For binary packages, use -* and then list the archs the bin package 73# For binary packages, use -* and then list the archs the bin package
55# exists for. If the package was for an x86 binary package, then 74# exists for. If the package was for an x86 binary package, then
56# KEYWORDS would be set like this: KEYWORDS="-* x86" 75# KEYWORDS would be set like this: KEYWORDS="-* x86"
57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 76# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58# compatibility reasons. 77# compatibility reasons.
59KEYWORDS="~x86" 78KEYWORDS="~x86"
60 79
61# Comprehensive list of any and all USE flags leveraged in the ebuild, 80# Comprehensive list of any and all USE flags leveraged in the ebuild,
62# with the exception of any ARCH specific flags, i.e. "ppc", "sparc", 81# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
63# "x86" and "alpha". This is a required variable. If the ebuild doesn't 82# "x86" and "alpha". This is a required variable. If the ebuild doesn't
64# use any USE flags, set to "". 83# use any USE flags, set to "".
65IUSE="X gnome" 84IUSE="gnome X"
85
86# A space delimited list of portage features to restrict. man 5 ebuild
87# for details. Usually not needed.
88#RESTRICT="strip"
66 89
67# Build-time dependencies, such as 90# Build-time dependencies, such as
68# ssl? ( >=dev-libs/openssl-0.9.6b ) 91# ssl? ( >=dev-libs/openssl-0.9.6b )
69# >=dev-lang/perl-5.6.1-r1 92# >=dev-lang/perl-5.6.1-r1
70# It is advisable to use the >= syntax show above, to reflect what you 93# It is advisable to use the >= syntax show above, to reflect what you
71# had installed on your system when you tested the package. Then 94# had installed on your system when you tested the package. Then
72# other users hopefully won't be caught without the right version of 95# other users hopefully won't be caught without the right version of
73# a dependency. 96# a dependency.
74DEPEND="" 97#DEPEND=""
75 98
76# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 99# Run-time dependencies. Must be defined to whatever this depends on to run.
77#RDEPEND="" 100# The below is valid if the same run-time depends are required to compile.
101RDEPEND="${DEPEND}"
78 102
79# Source directory; the dir where the sources can be found (automatically 103# Source directory; the dir where the sources can be found (automatically
80# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 104# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
81# If you don't need to change it, leave the S= line out of the ebuild 105# If you don't need to change it, leave the S= line out of the ebuild
82# to keep it tidy. 106# to keep it tidy.
83S=${WORKDIR}/${P} 107#S="${WORKDIR}/${P}"
84 108
109
110# The following src_compile function is implemented as default by portage, so
111# you only need to call it, if you need a different behaviour.
85src_compile() { 112#src_compile() {
86 # Most open-source packages use GNU autoconf for configuration. 113 # Most open-source packages use GNU autoconf for configuration.
114 # The default, quickest (and preferred) way of running configure is:
115 #econf
116 #
87 # You should use something similar to the following lines to 117 # You could use something similar to the following lines to
88 # configure your package before compilation. The "|| die" portion 118 # configure your package before compilation. The "|| die" portion
89 # at the end will stop the build process if the command fails. 119 # at the end will stop the build process if the command fails.
90 # You should use this at the end of critical commands in the build 120 # You should use this at the end of critical commands in the build
91 # process. (Hint: Most commands are critical, that is, the build 121 # process. (Hint: Most commands are critical, that is, the build
92 # process should abort if they aren't successful.) 122 # process should abort if they aren't successful.)
93 ./configure \ 123 #./configure \
94 --host=${CHOST} \ 124 # --host=${CHOST} \
95 --prefix=/usr \ 125 # --prefix=/usr \
96 --infodir=/usr/share/info \ 126 # --infodir=/usr/share/info \
97 --mandir=/usr/share/man || die "./configure failed" 127 # --mandir=/usr/share/man || die "./configure failed"
98 # Note the use of --infodir and --mandir, above. This is to make 128 # Note the use of --infodir and --mandir, above. This is to make
99 # this package FHS 2.2-compliant. For more information, see 129 # this package FHS 2.2-compliant. For more information, see
100 # http://www.pathname.com/fhs/ 130 # http://www.pathname.com/fhs/
101
102 # Also note that it is cleaner and easier to use econf, which is the
103 # portage shortcut to the above ./configure statement:
104 #
105 # econf || die
106 # Note that econf will die on failure, but please use econf || die
107 # for consistency.
108 131
109 # emake (previously known as pmake) is a script that calls the 132 # emake (previously known as pmake) is a script that calls the
110 # standard GNU make with parallel building options for speedier 133 # standard GNU make with parallel building options for speedier
111 # builds (especially on SMP systems). Try emake first. It might 134 # builds (especially on SMP systems). Try emake first. It might
112 # not work for some packages, because some makefiles have bugs 135 # not work for some packages, because some makefiles have bugs
113 # related to parallelism, in these cases, use emake -j1 to limit 136 # related to parallelism, in these cases, use emake -j1 to limit
114 # make to a single process. The -j1 is a visual clue to others 137 # make to a single process. The -j1 is a visual clue to others
115 # that the makefiles have bugs that have been worked around. 138 # that the makefiles have bugs that have been worked around.
139
116 emake || die "emake failed" 140 #emake || die "emake failed"
117} 141#}
118 142
119src_install() { 143src_install() {
120 # You must *personally verify* that this trick doesn't install 144 # You must *personally verify* that this trick doesn't install
121 # anything outside of DESTDIR; do this by reading and 145 # anything outside of DESTDIR; do this by reading and
122 # understanding the install part of the Makefiles. 146 # understanding the install part of the Makefiles.
123 make DESTDIR=${D} install || die 147 # This is the preferred way to install.
148 emake DESTDIR="${D}" install || die "emake install failed"
149
150 # When you hit a failure with emake, do not just use make. It is
151 # better to fix the Makefiles to allow proper parallelization.
152 # If you fail with that, use "emake -j1", it's still better than make.
153
124 # For Makefiles that don't make proper use of DESTDIR, setting 154 # For Makefiles that don't make proper use of DESTDIR, setting
125 # prefix is often an alternative. However if you do this, then 155 # prefix is often an alternative. However if you do this, then
126 # you also need to specify mandir and infodir, since they were 156 # you also need to specify mandir and infodir, since they were
127 # passed to ./configure as absolute paths (overriding the prefix 157 # passed to ./configure as absolute paths (overriding the prefix
128 # setting). 158 # setting).
129 #make \ 159 #emake \
130 # prefix=${D}/usr \ 160 # prefix="${D}"/usr \
131 # mandir=${D}/usr/share/man \ 161 # mandir="${D}"/usr/share/man \
132 # infodir=${D}/usr/share/info \ 162 # infodir="${D}"/usr/share/info \
133 # install || die 163 # libdir="${D}"/usr/$(get_libdir) \
164 # install || die "emake install failed"
134 # Again, verify the Makefiles! We don't want anything falling 165 # Again, verify the Makefiles! We don't want anything falling
135 # outside of ${D}. 166 # outside of ${D}.
136 167
137 # The portage shortcut to the above command is simply: 168 # The portage shortcut to the above command is simply:
138 # 169 #
139 #einstall || die 170 #einstall || die "einstall failed"
140 # Note that einstall will die on failure, but please use einstall || die
141 # for consistency.
142} 171}

Legend:
Removed from v.1.28  
changed lines
  Added in v.1.56

  ViewVC Help
Powered by ViewVC 1.1.20