/[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.20
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.20 2003/04/09 03:21:56 seemant 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 commited 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 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
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", "~sparc64"
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-independant (like Java, PHP or Perl
55# applications) specify all keywords. 53# applications) specify all keywords.
56# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 54# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
57# compatibility reasons. 55# compatibility reasons.
58KEYWORDS="x86" 56KEYWORDS="~x86"
57
58# Comprehensive list of any and all USE flags leveraged in the ebuild,
59# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
60# "sparc64", "x86" and "alpha". This is a required variable. If the
61# ebuild doesn't use any USE flags, set to "".
62IUSE="X gnome"
59 63
60# Build-time dependencies, such as 64# Build-time dependencies, such as
61# ssl? ( >=openssl-0.9.6b ) 65# ssl? ( >=openssl-0.9.6b )
62# >=perl-5.6.1-r1 66# >=perl-5.6.1-r1
63# It is advisable to use the >= syntax show above, to reflect what you 67# It is advisable to use the >= syntax show above, to reflect what you
70#RDEPEND="" 74#RDEPEND=""
71 75
72# Source directory; the dir where the sources can be found (automatically 76# Source directory; the dir where the sources can be found (automatically
73# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} 77# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
74# if you omit this line. 78# if you omit this line.
75
76S="${WORKDIR}/${P}" 79S=${WORKDIR}/${P}
77 80
78src_compile() { 81src_compile() {
79 # Most open-source packages use GNU autoconf for configuration. 82 # Most open-source packages use GNU autoconf for configuration.
80 # You should use something similar to the following lines to 83 # You should use something similar to the following lines to
81 # configure your package before compilation. The "|| die" portion 84 # configure your package before compilation. The "|| die" portion
89 --infodir=/usr/share/info \ 92 --infodir=/usr/share/info \
90 --mandir=/usr/share/man || die "./configure failed" 93 --mandir=/usr/share/man || die "./configure failed"
91 # Note the use of --infodir and --mandir, above. This is to make 94 # Note the use of --infodir and --mandir, above. This is to make
92 # this package FHS 2.2-compliant. For more information, see 95 # this package FHS 2.2-compliant. For more information, see
93 # http://www.pathname.com/fhs/ 96 # http://www.pathname.com/fhs/
97
98 # Also note that it is cleaner and easier to use econf, which is the
99 # portage shortcut to the above ./configure statement:
100 #
101 # econf || die
94 102
95 # emake (previously known as pmake) is a script that calls the 103 # emake (previously known as pmake) is a script that calls the
96 # standard GNU make with parallel building options for speedier 104 # standard GNU make with parallel building options for speedier
97 # builds (especially on SMP systems). Try emake first. It might 105 # builds (especially on SMP systems). Try emake first. It might
98 # not work for some packages, in which case you'll have to resort 106 # not work for some packages, in which case you'll have to resort
116 # mandir=${D}/usr/share/man \ 124 # mandir=${D}/usr/share/man \
117 # infodir=${D}/usr/share/info \ 125 # infodir=${D}/usr/share/info \
118 # install || die 126 # install || die
119 # Again, verify the Makefiles! We don't want anything falling 127 # Again, verify the Makefiles! We don't want anything falling
120 # outside of ${D}. 128 # outside of ${D}.
129
130 # The portage shortcut to the above command is simply:
131 #
132 #einstall || die
121} 133}

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

  ViewVC Help
Powered by ViewVC 1.1.20