/[gentoo-x86]/skel.ebuild
Gentoo

Diff of /skel.ebuild

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

Revision 1.48 Revision 1.55
1# Copyright 1999-2008 Gentoo Foundation 1# Copyright 1999-2011 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.48 2008/03/13 23:05:53 spb Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ebuild,v 1.55 2011/01/01 00:01:45 abcd 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.
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 13
14# The EAPI variable tells the ebuild format in use. 14# The EAPI variable tells the ebuild format in use.
15# Defaults to 0 if not specified. See current PMS draft for more details. 15# Defaults to 0 if not specified. The current PMS draft contains details on
16# a proposed EAPI=0 definition but is not finalized yet.
16# Eclasses will test for this variable if they need to use EAPI > 0 features. 17# Eclasses will test for this variable if they need to use EAPI > 0 features.
17# Ebuilds should not define EAPI=1 unless they need to use features added
18# in that version.
19#EAPI=1 18#EAPI=0
20 19
21# inherit lists eclasses to inherit functions from. Almost all ebuilds should 20# inherit lists eclasses to inherit functions from. Almost all ebuilds should
22# inherit eutils, as a large amount of important functionality has been 21# inherit eutils, as a large amount of important functionality has been
23# moved there. For example, the $(get_libdir) mentioned below wont work 22# moved there. For example, the epatch call mentioned below wont work
24# without the following line: 23# without the following line:
25inherit eutils 24inherit eutils
26# A well-used example of an eclass function that needs eutils is epatch. If 25# A well-used example of an eclass function that needs eutils is epatch. If
27# your source needs patches applied, it's suggested to put your patch in the 26# your source needs patches applied, it's suggested to put your patch in the
28# 'files' directory and use: 27# 'files' directory and use:
29# 28#
30# epatch ${FILESDIR}/patch-name-here 29# epatch "${FILESDIR}"/patch-name-here
31# 30#
32# eclasses tend to list descriptions of how to use their functions properly. 31# eclasses tend to list descriptions of how to use their functions properly.
33# take a look at /usr/portage/eclasses/ for more examples. 32# take a look at /usr/portage/eclasses/ for more examples.
34 33
35# Short one-line description of this package. 34# Short one-line description of this package.
93# >=dev-lang/perl-5.6.1-r1 92# >=dev-lang/perl-5.6.1-r1
94# It is advisable to use the >= syntax show above, to reflect what you 93# It is advisable to use the >= syntax show above, to reflect what you
95# had installed on your system when you tested the package. Then 94# had installed on your system when you tested the package. Then
96# other users hopefully won't be caught without the right version of 95# other users hopefully won't be caught without the right version of
97# a dependency. 96# a dependency.
98DEPEND="" 97#DEPEND=""
99 98
100# Run-time dependencies. Must be defined to whatever this depends on to run. 99# Run-time dependencies. Must be defined to whatever this depends on to run.
101# The below is valid if the same run-time depends are required to compile. 100# The below is valid if the same run-time depends are required to compile.
102RDEPEND="${DEPEND}" 101RDEPEND="${DEPEND}"
103 102
105# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} 104# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P}
106# If you don't need to change it, leave the S= line out of the ebuild 105# If you don't need to change it, leave the S= line out of the ebuild
107# to keep it tidy. 106# to keep it tidy.
108#S="${WORKDIR}/${P}" 107#S="${WORKDIR}/${P}"
109 108
109
110# The following src_compile function is implemented as default by portage, so
111# you only need to call it, if you need a different behaviour.
110src_compile() { 112#src_compile() {
111 # Most open-source packages use GNU autoconf for configuration. 113 # Most open-source packages use GNU autoconf for configuration.
112 # The quickest (and preferred) way of running configure is: 114 # The default, quickest (and preferred) way of running configure is:
113 econf || die "econf failed" 115 #econf
114 # 116 #
115 # You could use something similar to the following lines to 117 # You could use something similar to the following lines to
116 # configure your package before compilation. The "|| die" portion 118 # configure your package before compilation. The "|| die" portion
117 # at the end will stop the build process if the command fails. 119 # at the end will stop the build process if the command fails.
118 # You should use this at the end of critical commands in the build 120 # You should use this at the end of critical commands in the build
132 # builds (especially on SMP systems). Try emake first. It might 134 # builds (especially on SMP systems). Try emake first. It might
133 # not work for some packages, because some makefiles have bugs 135 # not work for some packages, because some makefiles have bugs
134 # related to parallelism, in these cases, use emake -j1 to limit 136 # related to parallelism, in these cases, use emake -j1 to limit
135 # make to a single process. The -j1 is a visual clue to others 137 # make to a single process. The -j1 is a visual clue to others
136 # that the makefiles have bugs that have been worked around. 138 # that the makefiles have bugs that have been worked around.
139
137 emake || die "emake failed" 140 #emake || die "emake failed"
138} 141#}
139 142
140src_install() { 143src_install() {
141 # You must *personally verify* that this trick doesn't install 144 # You must *personally verify* that this trick doesn't install
142 # anything outside of DESTDIR; do this by reading and 145 # anything outside of DESTDIR; do this by reading and
143 # understanding the install part of the Makefiles. 146 # understanding the install part of the Makefiles.

Legend:
Removed from v.1.48  
changed lines
  Added in v.1.55

  ViewVC Help
Powered by ViewVC 1.1.20