/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.14 Revision 1.22
1# Copyright 1999-2002 Gentoo Technologies, Inc. 1# Copyright 1999-2003 Gentoo Technologies, Inc.
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.14 2002/10/05 20:30:53 gerk Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.22 2003/07/18 19:54:38 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# comprehensive list of any and all USE flags leveraged in the build,
15# with the exception of any ARCH specific flags, i.e. ppc sparc sparc64
16# x86 alpha - this is a required variable
17IUSE="X gnome"
18 13
19# Short one-line description of this package. 14# Short one-line description of this package.
20DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
21 16
22# Homepage, not used by Portage directly but handy for developer reference 17# Homepage, not used by Portage directly but handy for developer reference
23HOMEPAGE="http://foo.bar.com" 18HOMEPAGE="http://foo.bar.com/"
24 19
25# Point to any required sources; these will be automatically downloaded by 20# Point to any required sources; these will be automatically downloaded by
26# Portage. 21# Portage.
27SRC_URI="ftp://foo.bar.com/${P}.tar.gz" 22SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
28 23
46 41
47# Using KEYWORDS, we can record masking information *inside* an ebuild 42# Using KEYWORDS, we can record masking information *inside* an ebuild
48# instead of relying on an external package.mask file. Right now, you 43# instead of relying on an external package.mask file. Right now, you
49# should set the KEYWORDS variable for every ebuild so that it contains 44# should set the KEYWORDS variable for every ebuild so that it contains
50# the names of all the architectures with which the ebuild works. We have 45# the names of all the architectures with which the ebuild works. We have
51# 4 official architecture names right now: "x86", "ppc", "sparc" and 46# 5 official architecture names right now: "~x86", "~ppc", "~sparc", "~sparc"
47# and "~alpha". The ~ in front of the architecture indicates that the
48# package is new and should be considered unstable until testing proves its
49# stability. Once packages go stable the ~ prefix is removed.
52# "sparc64". So, if you've confirmed that your ebuild works on x86 and ppc, 50# So, if you've confirmed that your ebuild works on x86 and ppc,
53# you'd specify: KEYWORDS="x86 ppc" 51# you'd specify: KEYWORDS="~x86 ~ppc"
54# For packages that are platform-independant (like Java, PHP or Perl 52# For packages that are platform-independent (like Java, PHP or Perl
55# applications) specify all keywords. 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"
56# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
57# compatibility reasons. 58# compatibility reasons.
58KEYWORDS="x86" 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# "sparc", "x86" and "alpha". This is a required variable. If the
64# ebuild doesn't use any USE flags, set to "".
65IUSE="X gnome"
59 66
60# Build-time dependencies, such as 67# Build-time dependencies, such as
61# ssl? ( >=openssl-0.9.6b ) 68# ssl? ( >=openssl-0.9.6b )
62# >=perl-5.6.1-r1 69# >=perl-5.6.1-r1
63# 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
70#RDEPEND="" 77#RDEPEND=""
71 78
72# Source directory; the dir where the sources can be found (automatically 79# Source directory; the dir where the sources can be found (automatically
73# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} 80# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
74# if you omit this line. 81# if you omit this line.
75
76S="${WORKDIR}/${P}" 82S=${WORKDIR}/${P}
77 83
78src_compile() { 84src_compile() {
79 # Most open-source packages use GNU autoconf for configuration. 85 # Most open-source packages use GNU autoconf for configuration.
80 # You should use something similar to the following lines to 86 # You should use something similar to the following lines to
81 # configure your package before compilation. The "|| die" portion 87 # configure your package before compilation. The "|| die" portion
89 --infodir=/usr/share/info \ 95 --infodir=/usr/share/info \
90 --mandir=/usr/share/man || die "./configure failed" 96 --mandir=/usr/share/man || die "./configure failed"
91 # Note the use of --infodir and --mandir, above. This is to make 97 # Note the use of --infodir and --mandir, above. This is to make
92 # this package FHS 2.2-compliant. For more information, see 98 # this package FHS 2.2-compliant. For more information, see
93 # http://www.pathname.com/fhs/ 99 # http://www.pathname.com/fhs/
100
101 # Also note that it is cleaner and easier to use econf, which is the
102 # portage shortcut to the above ./configure statement:
103 #
104 # econf || die
105 # Note that econf will die on failure, but plase use econf || die
106 # for consistency.
94 107
95 # emake (previously known as pmake) is a script that calls the 108 # emake (previously known as pmake) is a script that calls the
96 # standard GNU make with parallel building options for speedier 109 # standard GNU make with parallel building options for speedier
97 # builds (especially on SMP systems). Try emake first. It might 110 # builds (especially on SMP systems). Try emake first. It might
98 # not work for some packages, in which case you'll have to resort 111 # not work for some packages, in which case you'll have to resort
116 # mandir=${D}/usr/share/man \ 129 # mandir=${D}/usr/share/man \
117 # infodir=${D}/usr/share/info \ 130 # infodir=${D}/usr/share/info \
118 # install || die 131 # install || die
119 # Again, verify the Makefiles! We don't want anything falling 132 # Again, verify the Makefiles! We don't want anything falling
120 # outside of ${D}. 133 # outside of ${D}.
134
135 # The portage shortcut to the above command is simply:
136 #
137 #einstall || die
138 # Note that einstall will die on failure, but please use einstall || die
139 # for consistency.
121} 140}

Legend:
Removed from v.1.14  
changed lines
  Added in v.1.22

  ViewVC Help
Powered by ViewVC 1.1.20