/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.6 Revision 1.28
1# Copyright 1999-2002 Gentoo Technologies, Inc. 1# Copyright 1999-2004 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.6 2002/05/07 03:58:19 drobbins Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.28 2004/06/25 13:29:13 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 commited 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# Source directory; the dir where the sources can be found (automatically
15# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
16# if you omit this line.
17
18S=${WORKDIR}/${P}
19 13
20# Short one-line description of this package. 14# Short one-line description of this package.
21DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
16
17# Homepage, not used by Portage directly but handy for developer reference
18HOMEPAGE="http://foo.bar.com/"
22 19
23# Point to any required sources; these will be automatically downloaded by 20# Point to any required sources; these will be automatically downloaded by
24# Portage. 21# Portage.
25SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 22SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
26 23
27# Homepage, not used by Portage directly but handy for developer reference
28HOMEPAGE="http://"
29
30# License of the package. This must match the name of file(s) in 24# License of the package. This must match the name of file(s) in
31# /usr/portage/licenses/. For complex license combination see the developer 25# /usr/portage/licenses/. For complex license combination see the developer
32# docs on gentoo.org for details. 26# docs on gentoo.org for details.
33LICENSE="" 27LICENSE=""
34 28
29# The SLOT variable is used to tell Portage if it's OK to keep multiple
30# versions of the same package installed at the same time. For example,
31# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
32# with 1.2.2), it would be optimal to instruct Portage to not remove
33# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
34# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
35# emerge clean understands SLOTs, and will keep the most recent version
36# of each SLOT and remove everything else.
37# Note that normal applications should use SLOT="0" if possible, since
38# 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.
40SLOT="0"
41
42# Using KEYWORDS, we can record masking information *inside* an ebuild
43# instead of relying on an external package.mask file. Right now, you
44# should set the KEYWORDS variable for every ebuild so that it contains
45# the names of all the architectures with which the ebuild works. All of
46# the official architectures can be found in the keywords.desc file which
47# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
48# The ~ in front of the architecture indicates that the package is new and
49# should be considered unstable until testing proves its stability. Once
50# packages go stable the ~ prefix is removed. So, if you've confirmed that
51# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl
53# applications) specify all keywords.
54# 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
56# KEYWORDS would be set like this: KEYWORDS="-* x86"
57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58# compatibility reasons.
59KEYWORDS="~x86"
60
61# 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",
63# "x86" and "alpha". This is a required variable. If the ebuild doesn't
64# use any USE flags, set to "".
65IUSE="X gnome"
66
35# Build-time dependencies, such as 67# Build-time dependencies, such as
36# ssl? ( >=openssl-0.9.6b ) 68# ssl? ( >=dev-libs/openssl-0.9.6b )
37# >=perl-5.6.1-r1 69# >=dev-lang/perl-5.6.1-r1
38# It is advisable to use the >= syntax show above, to reflect what you 70# It is advisable to use the >= syntax show above, to reflect what you
39# had installed on your system when you tested the package. Then 71# had installed on your system when you tested the package. Then
40# other users hopefully won't be caught without the right version of 72# other users hopefully won't be caught without the right version of
41# a dependency. 73# a dependency.
42DEPEND="" 74DEPEND=""
43 75
44# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 76# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
45#RDEPEND="" 77#RDEPEND=""
78
79# Source directory; the dir where the sources can be found (automatically
80# 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
82# to keep it tidy.
83S=${WORKDIR}/${P}
46 84
47src_compile() { 85src_compile() {
48 # Most open-source packages use GNU autoconf for configuration. 86 # Most open-source packages use GNU autoconf for configuration.
49 # You should use something similar to the following lines to 87 # You should use something similar to the following lines to
50 # configure your package before compilation. The "|| die" portion 88 # configure your package before compilation. The "|| die" portion
58 --infodir=/usr/share/info \ 96 --infodir=/usr/share/info \
59 --mandir=/usr/share/man || die "./configure failed" 97 --mandir=/usr/share/man || die "./configure failed"
60 # Note the use of --infodir and --mandir, above. This is to make 98 # Note the use of --infodir and --mandir, above. This is to make
61 # this package FHS 2.2-compliant. For more information, see 99 # this package FHS 2.2-compliant. For more information, see
62 # http://www.pathname.com/fhs/ 100 # http://www.pathname.com/fhs/
63 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
64 # emake (previously known as pmake) is a script that calls the 109 # emake (previously known as pmake) is a script that calls the
65 # standard GNU make with parallel building options for speedier 110 # standard GNU make with parallel building options for speedier
66 # builds (especially on SMP systems). Try emake first. It might 111 # builds (especially on SMP systems). Try emake first. It might
67 # not work for some packages, in which case you'll have to resort 112 # not work for some packages, because some makefiles have bugs
68 # to normal "make". 113 # related to parallelism, in these cases, use emake -j1 to limit
69 emake || die 114 # make to a single process. The -j1 is a visual clue to others
70 #make || die 115 # that the makefiles have bugs that have been worked around.
116 emake || die "emake failed"
71} 117}
72 118
73src_install () { 119src_install() {
74 # You must *personally verify* that this trick doesn't install 120 # You must *personally verify* that this trick doesn't install
75 # anything outside of DESTDIR; do this by reading and 121 # anything outside of DESTDIR; do this by reading and
76 # understanding the install part of the Makefiles. 122 # understanding the install part of the Makefiles.
77 make DESTDIR=${D} install || die 123 make DESTDIR=${D} install || die
78 # For Makefiles that don't make proper use of DESTDIR, setting 124 # For Makefiles that don't make proper use of DESTDIR, setting
79 # prefix is often an alternative. However if you do this, then 125 # prefix is often an alternative. However if you do this, then
80 # you also need to specify mandir and infodir, since they were 126 # you also need to specify mandir and infodir, since they were
81 # passed to ./configure as absolute paths (overriding the prefix 127 # passed to ./configure as absolute paths (overriding the prefix
85 # mandir=${D}/usr/share/man \ 131 # mandir=${D}/usr/share/man \
86 # infodir=${D}/usr/share/info \ 132 # infodir=${D}/usr/share/info \
87 # install || die 133 # install || die
88 # Again, verify the Makefiles! We don't want anything falling 134 # Again, verify the Makefiles! We don't want anything falling
89 # outside of ${D}. 135 # outside of ${D}.
136
137 # The portage shortcut to the above command is simply:
138 #
139 #einstall || die
140 # Note that einstall will die on failure, but please use einstall || die
141 # for consistency.
90} 142}

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

  ViewVC Help
Powered by ViewVC 1.1.20