/[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.17
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 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.17 2002/11/08 22:03:45 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
55# applications) specify all keywords. 50# applications) specify all keywords.
56# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 51# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
57# compatibility reasons. 52# compatibility reasons.
58KEYWORDS="x86" 53KEYWORDS="x86"
59 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"
60
60# Build-time dependencies, such as 61# Build-time dependencies, such as
61# ssl? ( >=openssl-0.9.6b ) 62# ssl? ( >=openssl-0.9.6b )
62# >=perl-5.6.1-r1 63# >=perl-5.6.1-r1
63# 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
64# had installed on your system when you tested the package. Then 65# had installed on your system when you tested the package. Then
70#RDEPEND="" 71#RDEPEND=""
71 72
72# Source directory; the dir where the sources can be found (automatically 73# Source directory; the dir where the sources can be found (automatically
73# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P} 74# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}
74# if you omit this line. 75# if you omit this line.
75
76S="${WORKDIR}/${P}" 76S="${WORKDIR}/${P}"
77 77
78src_compile() { 78src_compile() {
79 # Most open-source packages use GNU autoconf for configuration. 79 # Most open-source packages use GNU autoconf for configuration.
80 # You should use something similar to the following lines to 80 # You should use something similar to the following lines to
89 --infodir=/usr/share/info \ 89 --infodir=/usr/share/info \
90 --mandir=/usr/share/man || die "./configure failed" 90 --mandir=/usr/share/man || die "./configure failed"
91 # Note the use of --infodir and --mandir, above. This is to make 91 # Note the use of --infodir and --mandir, above. This is to make
92 # this package FHS 2.2-compliant. For more information, see 92 # this package FHS 2.2-compliant. For more information, see
93 # http://www.pathname.com/fhs/ 93 # http://www.pathname.com/fhs/
94
95 # Also note that it is cleaner and easier to use econf, which is the
96 # portage shortcut to the above ./configure statement:
97 #
98 # econf
94 99
95 # emake (previously known as pmake) is a script that calls the 100 # emake (previously known as pmake) is a script that calls the
96 # standard GNU make with parallel building options for speedier 101 # standard GNU make with parallel building options for speedier
97 # builds (especially on SMP systems). Try emake first. It might 102 # builds (especially on SMP systems). Try emake first. It might
98 # not work for some packages, in which case you'll have to resort 103 # not work for some packages, in which case you'll have to resort
116 # mandir=${D}/usr/share/man \ 121 # mandir=${D}/usr/share/man \
117 # infodir=${D}/usr/share/info \ 122 # infodir=${D}/usr/share/info \
118 # install || die 123 # install || die
119 # Again, verify the Makefiles! We don't want anything falling 124 # Again, verify the Makefiles! We don't want anything falling
120 # outside of ${D}. 125 # outside of ${D}.
126
127 # The portage shortcut to the above command is simply:
128 #
129 #einstall || die
121} 130}

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

  ViewVC Help
Powered by ViewVC 1.1.20