/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.27 Revision 1.38
1# Copyright 1999-2004 Gentoo Technologies, Inc. 1# Copyright 1999-2006 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.27 2004/06/20 21:18:22 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.38 2006/06/23 15:50:35 genstef 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# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15# inherit eutils, as a large amount of important functionality has been
16# moved there. For example, the $(get_libdir) mentioned below wont work
17# without the following line:
18inherit eutils
19# 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
21# 'files' directory and use:
22#
23# epatch ${FILESDIR}/patch-name-here
24#
25# eclasses tend to list descriptions of how to use their functions properly.
26# take a look at /usr/portage/eclasses/ for more examples.
13 27
14# Short one-line description of this package. 28# Short one-line description of this package.
15DESCRIPTION="This is a sample skeleton ebuild file" 29DESCRIPTION="This is a sample skeleton ebuild file"
16 30
17# Homepage, not used by Portage directly but handy for developer reference 31# Homepage, not used by Portage directly but handy for developer reference
37# Note that normal applications should use SLOT="0" if possible, since 51# Note that normal applications should use SLOT="0" if possible, since
38# there should only be exactly one version installed at a time. 52# 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. 53# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
40SLOT="0" 54SLOT="0"
41 55
42# Using KEYWORDS, we can record masking information *inside* an ebuild 56# Using KEYWORDS, we can record masking information *inside* an ebuild
43# instead of relying on an external package.mask file. Right now, you 57# 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 58# 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 59# 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 60# architectures can be found in the keywords.desc file which is in
47# is in /usr/portage/profiles/. Usually you should just set this to "~x86". 61# /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 62# 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 63# 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 64# 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" 65# KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl 66# 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 67# 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 68# exists for. If the package was for an x86 binary package, then
56# KEYWORDS would be set like this: KEYWORDS="-* x86" 69# KEYWORDS would be set like this: KEYWORDS="-* x86"
57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 70# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58# compatibility reasons. 71# compatibility reasons.
61# Comprehensive list of any and all USE flags leveraged in the ebuild, 74# 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", 75# 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 76# "x86" and "alpha". This is a required variable. If the ebuild doesn't
64# use any USE flags, set to "". 77# use any USE flags, set to "".
65IUSE="X gnome" 78IUSE="X gnome"
79
80# A space delimited list of portage features to restrict. man 5 ebuild
81# for details. Usually not needed.
82#RESTRICT="strip"
66 83
67# Build-time dependencies, such as 84# Build-time dependencies, such as
68# ssl? ( >=dev-libs/openssl-0.9.6b ) 85# ssl? ( >=dev-libs/openssl-0.9.6b )
69# >=dev-lang/perl-5.6.1-r1 86# >=dev-lang/perl-5.6.1-r1
70# It is advisable to use the >= syntax show above, to reflect what you 87# It is advisable to use the >= syntax show above, to reflect what you
82# to keep it tidy. 99# to keep it tidy.
83S=${WORKDIR}/${P} 100S=${WORKDIR}/${P}
84 101
85src_compile() { 102src_compile() {
86 # Most open-source packages use GNU autoconf for configuration. 103 # Most open-source packages use GNU autoconf for configuration.
104 # The quickest (and preferred) way of running configure is:
105 econf || die "econf failed"
106 #
87 # You should use something similar to the following lines to 107 # You could use something similar to the following lines to
88 # configure your package before compilation. The "|| die" portion 108 # configure your package before compilation. The "|| die" portion
89 # at the end will stop the build process if the command fails. 109 # 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 110 # You should use this at the end of critical commands in the build
91 # process. (Hint: Most commands are critical, that is, the build 111 # process. (Hint: Most commands are critical, that is, the build
92 # process should abort if they aren't successful.) 112 # process should abort if they aren't successful.)
93 ./configure \ 113 #./configure \
94 --host=${CHOST} \ 114 # --host=${CHOST} \
95 --prefix=/usr \ 115 # --prefix=/usr \
96 --infodir=/usr/share/info \ 116 # --infodir=/usr/share/info \
97 --mandir=/usr/share/man || die "./configure failed" 117 # --mandir=/usr/share/man || die "./configure failed"
98 # Note the use of --infodir and --mandir, above. This is to make 118 # Note the use of --infodir and --mandir, above. This is to make
99 # this package FHS 2.2-compliant. For more information, see 119 # this package FHS 2.2-compliant. For more information, see
100 # http://www.pathname.com/fhs/ 120 # 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 121
109 # emake (previously known as pmake) is a script that calls the 122 # emake (previously known as pmake) is a script that calls the
110 # standard GNU make with parallel building options for speedier 123 # standard GNU make with parallel building options for speedier
111 # builds (especially on SMP systems). Try emake first. It might 124 # builds (especially on SMP systems). Try emake first. It might
112 # not work for some packages, because some makefiles have bugs 125 # not work for some packages, because some makefiles have bugs
118 131
119src_install() { 132src_install() {
120 # You must *personally verify* that this trick doesn't install 133 # You must *personally verify* that this trick doesn't install
121 # anything outside of DESTDIR; do this by reading and 134 # anything outside of DESTDIR; do this by reading and
122 # understanding the install part of the Makefiles. 135 # understanding the install part of the Makefiles.
123 make DESTDIR=${D} install || die 136 # This is the preferred way to install.
137 emake DESTDIR=${D} install || die "emake install failed"
138
139 # When you hit a failure with emake, do not just use make. It is
140 # better to fix the Makefiles to allow proper parallelization.
141 # If you fail with that, use "emake -j1", it's still better than make.
142
124 # For Makefiles that don't make proper use of DESTDIR, setting 143 # For Makefiles that don't make proper use of DESTDIR, setting
125 # prefix is often an alternative. However if you do this, then 144 # prefix is often an alternative. However if you do this, then
126 # you also need to specify mandir and infodir, since they were 145 # you also need to specify mandir and infodir, since they were
127 # passed to ./configure as absolute paths (overriding the prefix 146 # passed to ./configure as absolute paths (overriding the prefix
128 # setting). 147 # setting).
129 #make \ 148 #emake \
130 # prefix=${D}/usr \ 149 # prefix=${D}/usr \
131 # mandir=${D}/usr/share/man \ 150 # mandir=${D}/usr/share/man \
132 # infodir=${D}/usr/share/info \ 151 # infodir=${D}/usr/share/info \
133 # install || die 152 # libdir=${D}/usr/$(get_libdir) \
153 # install || die "emake install failed"
134 # Again, verify the Makefiles! We don't want anything falling 154 # Again, verify the Makefiles! We don't want anything falling
135 # outside of ${D}. 155 # outside of ${D}.
136 156
137 # The portage shortcut to the above command is simply: 157 # The portage shortcut to the above command is simply:
138 # 158 #
139 #einstall || die 159 #einstall || die "einstall failed"
140 # Note that einstall will die on failure, but please use einstall || die
141 # for consistency.
142} 160}

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

  ViewVC Help
Powered by ViewVC 1.1.20