/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.28 Revision 1.31
1# Copyright 1999-2004 Gentoo Foundation 1# Copyright 1999-2004 Gentoo Foundation
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.28 2004/06/25 13:29:13 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.31 2004/09/02 07:35:42 mr_bones_ 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 committed 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# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15# inherit eutils, as a large amount of important functionality has been
16# moved there. For example, the $(get_libdir) mentioned below wont work
17# without the following line:
18inherit eutils
19# A well-used example of an eclass function that needs eutils is epatch. If
20# your source needs patches applied, it's suggested to put your patch in the
21# 'files' directory and use:
22#
23# epatch ${FILESDIR}/patch-name-here
24#
25# eclasses tend to list descriptions of how to use their functions properly.
26# take a look at /usr/portage/eclasses/ for more examples.
13 27
14# Short one-line description of this package. 28# Short one-line description of this package.
15DESCRIPTION="This is a sample skeleton ebuild file" 29DESCRIPTION="This is a sample skeleton ebuild file"
16 30
17# Homepage, not used by Portage directly but handy for developer reference 31# Homepage, not used by Portage directly but handy for developer reference
47# is in /usr/portage/profiles/. Usually you should just set this to "~x86". 61# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
48# The ~ in front of the architecture indicates that the package is new and 62# The ~ in front of the architecture indicates that the package is new and
49# should be considered unstable until testing proves its stability. Once 63# should be considered unstable until testing proves its stability. Once
50# packages go stable the ~ prefix is removed. So, if you've confirmed that 64# packages go stable the ~ prefix is removed. So, if you've confirmed that
51# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc" 65# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
52# For packages that are platform-independent (like Java, PHP or Perl
53# applications) specify all keywords.
54# For binary packages, use -* and then list the archs the bin package 66# 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 67# exists for. If the package was for an x86 binary package, then
56# KEYWORDS would be set like this: KEYWORDS="-* x86" 68# KEYWORDS would be set like this: KEYWORDS="-* x86"
57# DO NOT USE KEYWORDS="*". This is deprecated and only for backward 69# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
58# compatibility reasons. 70# compatibility reasons.
61# Comprehensive list of any and all USE flags leveraged in the ebuild, 73# 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", 74# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
63# "x86" and "alpha". This is a required variable. If the ebuild doesn't 75# "x86" and "alpha". This is a required variable. If the ebuild doesn't
64# use any USE flags, set to "". 76# use any USE flags, set to "".
65IUSE="X gnome" 77IUSE="X gnome"
78
79# A space delimited list of portage features to restrict. man 5 ebuild
80# for details. Usually not needed.
81#RESTRICT="nostrip"
66 82
67# Build-time dependencies, such as 83# Build-time dependencies, such as
68# ssl? ( >=dev-libs/openssl-0.9.6b ) 84# ssl? ( >=dev-libs/openssl-0.9.6b )
69# >=dev-lang/perl-5.6.1-r1 85# >=dev-lang/perl-5.6.1-r1
70# It is advisable to use the >= syntax show above, to reflect what you 86# It is advisable to use the >= syntax show above, to reflect what you
128 # setting). 144 # setting).
129 #make \ 145 #make \
130 # prefix=${D}/usr \ 146 # prefix=${D}/usr \
131 # mandir=${D}/usr/share/man \ 147 # mandir=${D}/usr/share/man \
132 # infodir=${D}/usr/share/info \ 148 # infodir=${D}/usr/share/info \
149 # libdir=${D}/usr/$(get_libdir) \
133 # install || die 150 # install || die
134 # Again, verify the Makefiles! We don't want anything falling 151 # Again, verify the Makefiles! We don't want anything falling
135 # outside of ${D}. 152 # outside of ${D}.
136 153
137 # The portage shortcut to the above command is simply: 154 # The portage shortcut to the above command is simply:

Legend:
Removed from v.1.28  
changed lines
  Added in v.1.31

  ViewVC Help
Powered by ViewVC 1.1.20