/[gentoo-x86]/skel.ebuild

Diff of /skel.ebuild

Parent Directory | Revision Log | View Patch Patch

Revision 1.3		Revision 1.34
1	# Copyright 1999-2002 Gentoo Technologies, Inc.	1	# Copyright 1999-2005 Gentoo Foundation
2	# Distributed under the terms of the GNU General Public License, v2 or later	2	# Distributed under the terms of the GNU General Public License v2
3	# Maintainer: First Last <your email>
4	# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.3 2002/02/04 15:46:51 gbevin Exp $	3	# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.34 2005/01/01 05:46:55 dragonheart Exp $
5		4
6	# NOTE: The comments in this file are for instruction and	5	# NOTE: The comments in this file are for instruction and documentation.
7	# documentation. They're not meant to appear with your final,	6	# They're not meant to appear with your final, production ebuild. Please
8	# production ebuild. Please remember to remove them before submitting	7	# remember to remove them before submitting or committing your ebuild. That
9	# or committing your ebuild. That doesn't mean you can't add your own	8	# doesn't mean you can't add your own comments though.
10	# comments though.
11		9
12	# Remember to add the proper Author line, above.	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
		12	# generated to contain the correct data.
13		13
14	# The 'Header' on the fourth line should just be left alone.	14	# inherit lists eclasses to inherit functions from. Almost all ebuilds should
15	# When your ebuild will be commited to cvs, the details on that line will	15	# inherit eutils, as a large amount of important functionality has been
16	# be automatically generated to contain the correct data.	16	# moved there. For example, the $(get_libdir) mentioned below wont work
17		17	# without the following line:
18	# Source directory; the dir where the sources can be found	18	inherit eutils
19	# (automatically unpacked) inside ${WORKDIR}. Usually you can just	19	# A well-used example of an eclass function that needs eutils is epatch. If
20	# leave this as-is.	20	# your source needs patches applied, it's suggested to put your patch in the
21	S=${WORKDIR}/${P}	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.
22		27
23	# Short one-line description of this package.	28	# Short one-line description of this package.
24	DESCRIPTION="This is a sample skeleton ebuild file"	29	DESCRIPTION="This is a sample skeleton ebuild file"
25		30
		31	# Homepage, not used by Portage directly but handy for developer reference
		32	HOMEPAGE="http://foo.bar.com/"
		33
26	# Point to any required sources; these will be automatically	34	# Point to any required sources; these will be automatically downloaded by
27	# downloaded by Portage.	35	# Portage.
28	SRC_URI="ftp://foo.bar.com/${P}.tar.gz"	36	SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
29		37
30	# Homepage, not used by Portage directly but handy for developer reference	38	# License of the package. This must match the name of file(s) in
31	HOMEPAGE="http://"	39	# /usr/portage/licenses/. For complex license combination see the developer
		40	# docs on gentoo.org for details.
		41	LICENSE=""
		42
		43	# The SLOT variable is used to tell Portage if it's OK to keep multiple
		44	# versions of the same package installed at the same time. For example,
		45	# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
		46	# with 1.2.2), it would be optimal to instruct Portage to not remove
		47	# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
		48	# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
		49	# emerge clean understands SLOTs, and will keep the most recent version
		50	# of each SLOT and remove everything else.
		51	# Note that normal applications should use SLOT="0" if possible, since
		52	# there should only be exactly one version installed at a time.
		53	# DO NOT USE SLOT=""! This tells Portage to disable SLOTs for this package.
		54	SLOT="0"
		55
		56	# Using KEYWORDS, we can record masking information inside an ebuild
		57	# instead of relying on an external package.mask file. Right now, you
		58	# should set the KEYWORDS variable for every ebuild so that it contains
		59	# the names of all the architectures with which the ebuild works. All of
		60	# the official architectures can be found in the keywords.desc file which
		61	# is in /usr/portage/profiles/. Usually you should just set this to "~x86".
		62	# The ~ in front of the architecture indicates that the package is new and
		63	# should be considered unstable until testing proves its stability. Once
		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"
		69	# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
		70	# compatibility reasons.
		71	KEYWORDS="~x86"
		72
		73	# Comprehensive list of any and all USE flags leveraged in the ebuild,
		74	# with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
		75	# "x86" and "alpha". This is a required variable. If the ebuild doesn't
		76	# use any USE flags, set to "".
		77	IUSE="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"
32		82
33	# Build-time dependencies, such as	83	# Build-time dependencies, such as
34	# ssl ? ( >=openssl-0.9.6b )	84	# ssl? ( >=dev-libs/openssl-0.9.6b )
35	# >=perl-5.6.1-r1	85	# >=dev-lang/perl-5.6.1-r1
36	# 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
37	# had installed on your system when you tested the package. Then	87	# had installed on your system when you tested the package. Then
38	# 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
39	# a dependency.	89	# a dependency.
40	DEPEND=""	90	DEPEND=""
41		91
42	# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:	92	# Run-time dependencies, same as DEPEND if RDEPEND isn't defined:
43	#RDEPEND=""	93	#RDEPEND=""
44		94
		95	# Source directory; the dir where the sources can be found (automatically
		96	# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
		97	# If you don't need to change it, leave the S= line out of the ebuild
		98	# to keep it tidy.
		99	S=${WORKDIR}/${P}
		100
45	src_compile() {	101	src_compile() {
46	# Most open-source packages use GNU autoconf for configuration.	102	# Most open-source packages use GNU autoconf for configuration.
		103	# The quickest (and preferred) way of running configure is:
		104	econf \|\| die "econf failed"
		105	#
47	# You should use something similar to the following lines to	106	# You could use something similar to the following lines to
48	# configure your package before compilation. The "\|\| die" portion	107	# configure your package before compilation. The "\|\| die" portion
49	# at the end will stop the build process if the command fails.	108	# at the end will stop the build process if the command fails.
50	# You should use this at the end of critical commands in the build	109	# You should use this at the end of critical commands in the build
51	# process. (Hint: Most commands are critical, that is, the build	110	# process. (Hint: Most commands are critical, that is, the build
52	# process should abort if they aren't successful.)	111	# process should abort if they aren't successful.)
53	./configure \	112	#./configure \
54	--host=${CHOST} \	113	# --host=${CHOST} \
55	--prefix=/usr \	114	# --prefix=/usr \
56	--infodir=/usr/share/info \	115	# --infodir=/usr/share/info \
57	--mandir=/usr/share/man \|\| die "./configure failed"	116	# --mandir=/usr/share/man \|\| die "./configure failed"
58	# Note the use of --infodir and --mandir, above. This is to make	117	# Note the use of --infodir and --mandir, above. This is to make
59	# this package FHS 2.2-compliant. For more information, see	118	# this package FHS 2.2-compliant. For more information, see
60	# http://www.pathname.com/fhs/	119	# http://www.pathname.com/fhs/
61		120
62	# emake (previously known as pmake) is a script that calls the	121	# emake (previously known as pmake) is a script that calls the
63	# standard GNU make with parallel building options for speedier	122	# standard GNU make with parallel building options for speedier
64	# builds (especially on SMP systems). Try emake first. It might	123	# builds (especially on SMP systems). Try emake first. It might
65	# not work for some packages, in which case you'll have to resort	124	# not work for some packages, because some makefiles have bugs
66	# to normal "make".	125	# related to parallelism, in these cases, use emake -j1 to limit
67	emake \|\| die	126	# make to a single process. The -j1 is a visual clue to others
68	#make \|\| die	127	# that the makefiles have bugs that have been worked around.
		128	emake \|\| die "emake failed"
69	}	129	}
70		130
71	src_install () {	131	src_install() {
72	# You must personally verify that this trick doesn't install	132	# You must personally verify that this trick doesn't install
73	# anything outside of DESTDIR; do this by reading and	133	# anything outside of DESTDIR; do this by reading and
74	# understanding the install part of the Makefiles.	134	# understanding the install part of the Makefiles.
		135	# This is the preferred way to install.
75	make DESTDIR=${D} install \|\| die	136	make DESTDIR=${D} install \|\| die
		137
76	# For Makefiles that don't make proper use of DESTDIR, setting	138	# For Makefiles that don't make proper use of DESTDIR, setting
77	# prefix is often an alternative. However if you do this, then	139	# prefix is often an alternative. However if you do this, then
78	# you also need to specify mandir and infodir, since they were	140	# you also need to specify mandir and infodir, since they were
79	# passed to ./configure as absolute paths (overriding the prefix	141	# passed to ./configure as absolute paths (overriding the prefix
80	# setting).	142	# setting).
81	#make \	143	#make \
82	# prefix=${D}/usr \	144	# prefix=${D}/usr \
83	# mandir=${D}/usr/share/man \	145	# mandir=${D}/usr/share/man \
84	# infodir=${D}/usr/share/info \	146	# infodir=${D}/usr/share/info \
		147	# libdir=${D}/usr/$(get_libdir) \
85	# install \|\| die	148	# install \|\| die
86	# Again, verify the Makefiles! We don't want anything falling	149	# Again, verify the Makefiles! We don't want anything falling
87	# outside of ${D}.	150	# outside of ${D}.
		151
		152	# The portage shortcut to the above command is simply:
		153	#
		154	#einstall \|\| die
88	}	155	}

 Legend:



Removed from v.1.3
 


changed lines


 
Added in v.1.34
 Legend:



Removed from v.1.3
 


changed lines


 
Added in v.1.34
-Removed from v.1.3
+Added in v.1.34

	ViewVC Help
Powered by ViewVC 1.1.13