/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.20 Revision 1.22
1# Copyright 1999-2003 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.20 2003/04/09 03:21:56 seemant 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 13
14# Short one-line description of this package. 14# Short one-line description of this package.
15DESCRIPTION="This is a sample skeleton ebuild file" 15DESCRIPTION="This is a sample skeleton ebuild file"
16 16
41 41
42# Using KEYWORDS, we can record masking information *inside* an ebuild 42# Using KEYWORDS, we can record masking information *inside* an ebuild
43# 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
44# 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
45# 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
46# 5 official architecture names right now: "~x86", "~ppc", "~sparc", "~sparc64" 46# 5 official architecture names right now: "~x86", "~ppc", "~sparc", "~sparc"
47# and "~alpha". The ~ in front of the architecture indicates that the 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 48# package is new and should be considered unstable until testing proves its
49# stability. Once packages go stable the ~ prefix is removed. 49# stability. Once packages go stable the ~ prefix is removed.
50# 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,
51# you'd specify: KEYWORDS="~x86 ~ppc" 51# you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independant (like Java, PHP or Perl 52# For packages that are platform-independent (like Java, PHP or Perl
53# 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"
54# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
55# compatibility reasons. 58# compatibility reasons.
56KEYWORDS="~x86" 59KEYWORDS="~x86"
57 60
58# Comprehensive list of any and all USE flags leveraged in the ebuild, 61# 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", 62# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
60# "sparc64", "x86" and "alpha". This is a required variable. If the 63# "sparc", "x86" and "alpha". This is a required variable. If the
61# ebuild doesn't use any USE flags, set to "". 64# ebuild doesn't use any USE flags, set to "".
62IUSE="X gnome" 65IUSE="X gnome"
63 66
64# Build-time dependencies, such as 67# Build-time dependencies, such as
65# ssl? ( >=openssl-0.9.6b ) 68# ssl? ( >=openssl-0.9.6b )
97 100
98 # Also note that it is cleaner and easier to use econf, which is the 101 # Also note that it is cleaner and easier to use econf, which is the
99 # portage shortcut to the above ./configure statement: 102 # portage shortcut to the above ./configure statement:
100 # 103 #
101 # econf || die 104 # econf || die
105 # Note that econf will die on failure, but plase use econf || die
106 # for consistency.
102 107
103 # emake (previously known as pmake) is a script that calls the 108 # emake (previously known as pmake) is a script that calls the
104 # standard GNU make with parallel building options for speedier 109 # standard GNU make with parallel building options for speedier
105 # builds (especially on SMP systems). Try emake first. It might 110 # builds (especially on SMP systems). Try emake first. It might
106 # 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
128 # outside of ${D}. 133 # outside of ${D}.
129 134
130 # The portage shortcut to the above command is simply: 135 # The portage shortcut to the above command is simply:
131 # 136 #
132 #einstall || die 137 #einstall || die
138 # Note that einstall will die on failure, but please use einstall || die
139 # for consistency.
133} 140}

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

  ViewVC Help
Powered by ViewVC 1.1.20