/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.5 Revision 1.15
1# Copyright 1999-2002 Gentoo Technologies, Inc. 1# Copyright 1999-2002 Gentoo Technologies, Inc.
2# Distributed under the terms of the GNU General Public License, v2 or later 2# Distributed under the terms of the GNU General Public License v2
3# Maintainer: First Last <your email>
4# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.5 2002/04/29 22:56:53 sandymac Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.15 2002/10/18 18:52:09 blizzy Exp $
5 4
6# NOTE: The comments in this file are for instruction and 5# NOTE: The comments in this file are for instruction and documentation.
7# documentation. They're not meant to appear with your final, 6# They're not meant to appear with your final, production ebuild. Please
8# production ebuild. Please remember to remove them before submitting 7# remember to remove them before submitting or committing your ebuild. That
9# or committing your ebuild. That doesn't mean you can't add your own 8# doesn't mean you can't add your own comments though.
10# comments though.
11 9
12# Remember to add the proper Author line, above.
13
14# The 'Header' on the fourth line should just be left alone. 10# The 'Header' on the third line should just be left alone. When your ebuild
15# When your ebuild will be commited to cvs, the details on that line will 11# will be commited to cvs, the details on that line will be automatically
16# be automatically generated to contain the correct data. 12# generated to contain the correct data.
17
18# Source directory; the dir where the sources can be found
19# (automatically unpacked) inside ${WORKDIR}. Usually you can just
20# leave this as-is.
21S=${WORKDIR}/${P}
22 13
23# Short one-line description of this package. 14# Short one-line description of this package.
24DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
25 16
17# Homepage, not used by Portage directly but handy for developer reference
18HOMEPAGE="http://foo.bar.com"
19
26# Point to any required sources; these will be automatically 20# Point to any required sources; these will be automatically downloaded by
27# downloaded by Portage. 21# Portage.
28SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 22SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
29
30# Homepage, not used by Portage directly but handy for developer reference
31HOMEPAGE="http://"
32 23
33# 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
34# /usr/portage/licenses/. For complex license combination see the developer 25# /usr/portage/licenses/. For complex license combination see the developer
35# docs on gentoo.org for details. 26# docs on gentoo.org for details.
36LICENSE="" 27LICENSE=""
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. We have
46# 4 official architecture names right now: "x86", "ppc", "sparc" and
47# "sparc64". So, if you've confirmed that your ebuild works on x86 and ppc,
48# you'd specify: KEYWORDS="x86 ppc"
49# For packages that are platform-independant (like Java, PHP or Perl
50# applications) specify all keywords.
51# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
52# compatibility reasons.
53KEYWORDS="x86"
54
55# Comprehensive list of any and all USE flags leveraged in the ebuild,
56# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
57# "sparc64", "x86" and "alpha". This is a required variable. If the
58# ebuild doesn't use any USE flags, set to "".
59IUSE="X gnome"
37 60
38# Build-time dependencies, such as 61# Build-time dependencies, such as
39# ssl? ( >=openssl-0.9.6b ) 62# ssl? ( >=openssl-0.9.6b )
40# >=perl-5.6.1-r1 63# >=perl-5.6.1-r1
41# It is advisable to use the >= syntax show above, to reflect what you 64# It is advisable to use the >= syntax show above, to reflect what you
… …
44# a dependency. 67# a dependency.
45DEPEND="" 68DEPEND=""
46 69
47# Run-time dependencies, same as DEPEND if RDEPEND isn't defined: 70# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
48#RDEPEND="" 71#RDEPEND=""
72
73# Source directory; the dir where the sources can be found (automatically
74# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
75# if you omit this line.
76
77S="${WORKDIR}/${P}"
49 78
50src_compile() { 79src_compile() {
51 # Most open-source packages use GNU autoconf for configuration. 80 # Most open-source packages use GNU autoconf for configuration.
52 # You should use something similar to the following lines to 81 # You should use something similar to the following lines to
53 # configure your package before compilation. The "|| die" portion 82 # configure your package before compilation. The "|| die" portion
… …
61 --infodir=/usr/share/info \ 90 --infodir=/usr/share/info \
62 --mandir=/usr/share/man || die "./configure failed" 91 --mandir=/usr/share/man || die "./configure failed"
63 # Note the use of --infodir and --mandir, above. This is to make 92 # Note the use of --infodir and --mandir, above. This is to make
64 # this package FHS 2.2-compliant. For more information, see 93 # this package FHS 2.2-compliant. For more information, see
65 # http://www.pathname.com/fhs/ 94 # http://www.pathname.com/fhs/
66 95
67 # emake (previously known as pmake) is a script that calls the 96 # emake (previously known as pmake) is a script that calls the
68 # standard GNU make with parallel building options for speedier 97 # standard GNU make with parallel building options for speedier
69 # builds (especially on SMP systems). Try emake first. It might 98 # builds (especially on SMP systems). Try emake first. It might
70 # not work for some packages, in which case you'll have to resort 99 # not work for some packages, in which case you'll have to resort
71 # to normal "make". 100 # to normal "make".
72 emake || die 101 emake || die
73 #make || die 102 #make || die
74} 103}
75 104
76src_install () { 105src_install() {
77 # You must *personally verify* that this trick doesn't install 106 # You must *personally verify* that this trick doesn't install
78 # anything outside of DESTDIR; do this by reading and 107 # anything outside of DESTDIR; do this by reading and
79 # understanding the install part of the Makefiles. 108 # understanding the install part of the Makefiles.
80 make DESTDIR=${D} install || die 109 make DESTDIR=${D} install || die
81 # For Makefiles that don't make proper use of DESTDIR, setting 110 # For Makefiles that don't make proper use of DESTDIR, setting
82 # prefix is often an alternative. However if you do this, then 111 # prefix is often an alternative. However if you do this, then
83 # you also need to specify mandir and infodir, since they were 112 # you also need to specify mandir and infodir, since they were
84 # passed to ./configure as absolute paths (overriding the prefix 113 # passed to ./configure as absolute paths (overriding the prefix
Legend:
Removed from v.1.5  
changed lines
  Added in v.1.15
  ViewVC Help
Powered by ViewVC 1.1.13