/[gentoo-x86]/skel.ebuild

Diff of /skel.ebuild

Parent Directory | Revision Log | View Patch Patch

Revision 1.15		Revision 1.31
1	# Copyright 1999-2002 Gentoo Technologies, Inc.	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.15 2002/10/18 18:52:09 blizzy 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 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	# 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:
		18	inherit 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.
15	DESCRIPTION="This is a sample skeleton ebuild file"	29	DESCRIPTION="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
18	HOMEPAGE="http://foo.bar.com"	32	HOMEPAGE="http://foo.bar.com/"
19		33
20	# Point to any required sources; these will be automatically downloaded by	34	# Point to any required sources; these will be automatically downloaded by
21	# Portage.	35	# Portage.
22	SRC_URI="ftp://foo.bar.com/${P}.tar.gz"	36	SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
23		37
24	# License of the package. This must match the name of file(s) in	38	# License of the package. This must match the name of file(s) in
25	# /usr/portage/licenses/. For complex license combination see the developer	39	# /usr/portage/licenses/. For complex license combination see the developer
26	# docs on gentoo.org for details.	40	# docs on gentoo.org for details.
27	LICENSE=""	41	LICENSE=""
28		42
29	# The SLOT variable is used to tell Portage if it's OK to keep multiple	43	# The SLOT variable is used to tell Portage if it's OK to keep multiple
30	# versions of the same package installed at the same time. For example,	44	# versions of the same package installed at the same time. For example,
31	# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible	45	# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
32	# with 1.2.2), it would be optimal to instruct Portage to not remove	46	# with 1.2.2), it would be optimal to instruct Portage to not remove
33	# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,	47	# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
34	# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.	48	# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
35	# emerge clean understands SLOTs, and will keep the most recent version	49	# emerge clean understands SLOTs, and will keep the most recent version
36	# of each SLOT and remove everything else.	50	# of each SLOT and remove everything else.
37	# Note that normal applications should use SLOT="0" if possible, since	51	# Note that normal applications should use SLOT="0" if possible, since
38	# there should only be exactly one version installed at a time.	52	# there should only be exactly one version installed at a time.
39	# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.	53	# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
40	SLOT="0"	54	SLOT="0"
41		55
42	# Using KEYWORDS, we can record masking information inside an ebuild	56	# Using KEYWORDS, we can record masking information inside an ebuild
43	# instead of relying on an external package.mask file. Right now, you	57	# 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	58	# 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	59	# the names of all the architectures with which the ebuild works. All of
46	# 4 official architecture names right now: "x86", "ppc", "sparc" and	60	# the official architectures can be found in the keywords.desc file which
47	# "sparc64". So, if you've confirmed that your ebuild works on x86 and ppc,	61	# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
48	# you'd specify: KEYWORDS="x86 ppc"	62	# The ~ in front of the architecture indicates that the package is new and
49	# For packages that are platform-independant (like Java, PHP or Perl	63	# should be considered unstable until testing proves its stability. Once
50	# applications) specify all keywords.	64	# packages go stable the ~ prefix is removed. So, if you've confirmed that
		65	# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
		66	# For binary packages, use -* and then list the archs the bin package
		67	# exists for. If the package was for an x86 binary package, then
		68	# KEYWORDS would be set like this: KEYWORDS="-* x86"
51	# DO NOT USE KEYWORDS="*". This is deprecated and only for backward	69	# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
52	# compatibility reasons.	70	# compatibility reasons.
53	KEYWORDS="x86"	71	KEYWORDS="~x86"
54		72
55	# 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,
56	# 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",
57	# "sparc64", "x86" and "alpha". This is a required variable. If the	75	# "x86" and "alpha". This is a required variable. If the ebuild doesn't
58	# ebuild doesn't use any USE flags, set to "".	76	# use any USE flags, set to "".
59	IUSE="X gnome"	77	IUSE="X gnome"
60		78
		79	# A space delimited list of portage features to restrict. man 5 ebuild
		80	# for details. Usually not needed.
		81	#RESTRICT="nostrip"
		82
61	# Build-time dependencies, such as	83	# Build-time dependencies, such as
62	# ssl? ( >=openssl-0.9.6b )	84	# ssl? ( >=dev-libs/openssl-0.9.6b )
63	# >=perl-5.6.1-r1	85	# >=dev-lang/perl-5.6.1-r1
64	# 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
65	# had installed on your system when you tested the package. Then	87	# had installed on your system when you tested the package. Then
66	# other users hopefully won't be caught without the right version of	88	# other users hopefully won't be caught without the right version of
67	# a dependency.	89	# a dependency.
68	DEPEND=""	90	DEPEND=""
69		91
70	# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:	92	# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
71	#RDEPEND=""	93	#RDEPEND=""
72		94
73	# Source directory; the dir where the sources can be found (automatically	95	# Source directory; the dir where the sources can be found (automatically
74	# unpacked) inside ${WORKDIR}. S will get a default setting of ${WORKDIR}/${P}	96	# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
75	# if you omit this line.	97	# If you don't need to change it, leave the S= line out of the ebuild
76		98	# to keep it tidy.
77	S="${WORKDIR}/${P}"	99	S=${WORKDIR}/${P}
78		100
79	src_compile() {	101	src_compile() {
80	# Most open-source packages use GNU autoconf for configuration.	102	# Most open-source packages use GNU autoconf for configuration.
81	# You should use something similar to the following lines to	103	# You should use something similar to the following lines to
82	# configure your package before compilation. The "\|\| die" portion	104	# configure your package before compilation. The "\|\| die" portion
…		…
91	--mandir=/usr/share/man \|\| die "./configure failed"	113	--mandir=/usr/share/man \|\| die "./configure failed"
92	# Note the use of --infodir and --mandir, above. This is to make	114	# Note the use of --infodir and --mandir, above. This is to make
93	# this package FHS 2.2-compliant. For more information, see	115	# this package FHS 2.2-compliant. For more information, see
94	# http://www.pathname.com/fhs/	116	# http://www.pathname.com/fhs/
95		117
		118	# Also note that it is cleaner and easier to use econf, which is the
		119	# portage shortcut to the above ./configure statement:
		120	#
		121	# econf \|\| die
		122	# Note that econf will die on failure, but please use econf \|\| die
		123	# for consistency.
		124
96	# emake (previously known as pmake) is a script that calls the	125	# emake (previously known as pmake) is a script that calls the
97	# standard GNU make with parallel building options for speedier	126	# standard GNU make with parallel building options for speedier
98	# builds (especially on SMP systems). Try emake first. It might	127	# builds (especially on SMP systems). Try emake first. It might
99	# not work for some packages, in which case you'll have to resort	128	# not work for some packages, because some makefiles have bugs
100	# to normal "make".	129	# related to parallelism, in these cases, use emake -j1 to limit
101	emake \|\| die	130	# make to a single process. The -j1 is a visual clue to others
102	#make \|\| die	131	# that the makefiles have bugs that have been worked around.
		132	emake \|\| die "emake failed"
103	}	133	}
104		134
105	src_install() {	135	src_install() {
106	# You must personally verify that this trick doesn't install	136	# You must personally verify that this trick doesn't install
107	# anything outside of DESTDIR; do this by reading and	137	# anything outside of DESTDIR; do this by reading and
…		…
114	# setting).	144	# setting).
115	#make \	145	#make \
116	# prefix=${D}/usr \	146	# prefix=${D}/usr \
117	# mandir=${D}/usr/share/man \	147	# mandir=${D}/usr/share/man \
118	# infodir=${D}/usr/share/info \	148	# infodir=${D}/usr/share/info \
		149	# libdir=${D}/usr/$(get_libdir) \
119	# install \|\| die	150	# install \|\| die
120	# Again, verify the Makefiles! We don't want anything falling	151	# Again, verify the Makefiles! We don't want anything falling
121	# outside of ${D}.	152	# outside of ${D}.
		153
		154	# The portage shortcut to the above command is simply:
		155	#
		156	#einstall \|\| die
		157	# Note that einstall will die on failure, but please use einstall \|\| die
		158	# for consistency.
122	}	159	}

 Legend:



Removed from v.1.15
 


changed lines


 
Added in v.1.31
 Legend:



Removed from v.1.15
 


changed lines


 
Added in v.1.31
-Removed from v.1.15
+Added in v.1.31

	ViewVC Help
Powered by ViewVC 1.1.20