+++ /dev/null
-.TH ALTERNATIVES.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-alternatives \- interface for SLOT'ed packages requiring a symbolic link to the
-latest version
-.SH DESCRIPTION
-The \fBalternatives\fR eclass provides an interface for SLOT'ed packages that
-require a symbolic link that points to the latest version installed. Due to the
-varying order in which SLOT'ed versions may be installed, the symbolic link is
-not always guaranteed to point to the latest version. The \fBalternatives\fR
-eclass attempts to solve this problem.
-.br
-
-There are currently two methods in which this eclass may be used. The first
-method involves variable invocation (via \fBSOURCE\fR and \fBALTERNATIVES\fR),
-while the second method involves function invocation (via \fBalternatives_makesym\fR
-or \fBalternatives_auto_makesym\fR). These will be described below, however,
-please keep in mind that the two methods are not meant to be used in conjunction.
-.SH VARIABLES
-.TP
-.B SOURCE = \fI"/usr/bin/python"\fR
-Defines the name of the symbolic link that will be created to point to the
-latest installed version.
-.TP
-.B ALTERNATIVES = \fI"/usr/bin/python2.3 /usr/bin/python2.2"\fR
-Defines a whitespace-delimited list of alternatives. The first one found to
-exist will become the target of the created symbolic link.
-.SH FUNCTIONS
-.TP
-.B alternatives_makesym \fI< symlink > < alt1 alt2 ... >\fR
-Creates the specified symbolic link to point to the first specified alternative
-found to exist. This function is normally invoked from \fBpkg_postinst\fR and
-\fBpkg_postrm\fR.
-.TP
-.B alternatives_auto_makesym \fI< symlink > < alt_glob >\fR
-A "smart" version of \fBalternatives_makesym\fR that attempts to automatically
-deduce which version to link to, based on the specified alternatives glob
-pattern (eg. "python[0-9].[0-9]"). Like \fBalternatives_makesym\fR, this
-function is normally invoked from \fBpkg_postinst\fR and \fBpkg_postrm\fR.
-.TP
-\fBNOTE\fR: the following default pkg functions are only meant for use with the
-variable invocation method.
-.TP
-.B alternatives_pkg_postinst
-Default pkg_postinst that calls \fBalternatives_makesym\fR if both the
-\fBSOURCE\fR and \fBALTERNATIVES\fR variables are set.
-.TP
-.B alternatives_pkg_postrm
-Default pkg_postrm that calls \fBalternatives_makesym\fR if both the \fBSOURCE\fR
-and \fBALTERNATIVES\fR variables are set.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/alternatives.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/alternatives.eclass.5,v 1.1.2.1 2005/08/20 05:05:31 vapier Exp $
+++ /dev/null
-.TH "CHECK-KERNEL.ECLASS" "5" "Aug 2004" "Portage 2.0.51" "portage"
-.SH "NAME"
-check-kernel.eclass \- check kernel sources
-.SH "DESCRIPTION"
-The \fBcheck-kernel\fR eclass provides an easy interface for detecting kernel
-sources and retrieving various information.
-.SH "VARIABLES"
-The following variables are exported by the \fBcheck-kernel\fR eclass:
-.TP
-.BR KV_full
-Full kernel version (eg. 2.4.27-gentoo-r1)
-.TP
-.BR KV_major
-Major kernel version (eg. 2)
-.TP
-.BR KV_minor
-Minor kernel version (eg. 4)
-.TP
-.BR KV_micro
-Micro kernel version (eg. 27)
-.SH "FUNCTIONS"
-.TP
-.BR check_version_h
-Checks to make sure the /usr/src/linux symlink is correctly setup. If it is not,
-this function will print a huge error message and halt the emerge process.
-.TP
-.BR get_KV_info
-Parses the kernel's version.h to fill in the \fB${KV_full}\fR, \fB${KV_major}\fR,
-\fB${KV_minor}\fR, and \fB${KV_micro}\fR variables.
-.TP
-\fINOTE:\fR The following functions all return shell true/false.
-.TP
-.BR is_2_4_kernel
-Checks for kernel version 2.4.
-.TP
-.BR is_2_5_kernel
-Checks for kernel version 2.5.
-.TP
-.BR is_2_6_kernel
-Checks for kernel version 2.6.
-.TP
-.BR kernel_supports_modules
-Check to see if the kernel supports modules (CONFIG_MODULES).
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/check-kernel.eclass
-.SH "AUTHORS"
-Aaron Walker <ka0ttic@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/check-kernel.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH CHECK-REQS.ECLASS 5 "Dec 2004" "Portage 2.0.51" "portage"
-.SH NAME
-check-reqs.eclass \- functions for checking proper build requirements
-.SH DESCRIPTION
-The \fBcheck-reqs\fR eclass provides a uniform interface for handling ebuilds
-which require an abnormally high amount of system resources. The variable(s)
-and function(s) mentioned here should usually be set/called from \fBpkg_setup\fR.
-.br
-
-\fBNOTE\fR: Minimum criteria for use of this eclass is a build that requires
->256MB of RAM and/or >1GB of temporary or install space.
-.SH VARIABLES
-\fBNOTE\fR: all numerical values are evaluated as megabytes (MB).
-.TP
-.B CHECKREQS_ACTION = \fI"(warn|error|ignore)"\fR
-Defines action to take if current system resources do not satisfy requirements.
-\fBNOTE\fR: this variable is for end user only. Ebuilds must *not* override or
-set a default for this variable.
-.TP
-.B CHECKREQS_MEMORY = \fI"256"\fR
-Defines amount of memory required. Note that the \fBcheck-reqs\fR eclass does
-not take swap space into account when checking current memory resources.
-.TP
-.B CHECKREQS_DISK_BUILD = \fI"1024"\fR
-Defines amount of temporary build space required.
-.TP
-.B CHECKREQS_DISK_USR = \fI"1024"\fR
-Defines amount of /usr space required.
-.TP
-.B CHECKREQS_DISK_VAR = \fI"1024"\fR
-Defines amount of /var space required.
-.SH FUNCTIONS
-\fBNOTE\fR: all numerical values are evaluated as megabytes (MB). Any values
-should merely be rough estimates, and a high degree of precision should not
-be implied -- for example, "2048" (or "2000") are more appropriate than "2137".
-.TP
-.B check_reqs
-Performs resource checks based on above defined variables. If the checks fail,
-the action specified by \fBCHECKREQS_ACTION\fR will be executed. If for some
-reason the \fBcheck-reqs\fR eclass is unable to determine current resources,
-then no action will be performed. This function should be called from within
-\fBpkg_setup\fR.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/check-reqs.eclass
-.SH AUTHORS
-.nf
-Aaron Walker <ka0ttic@gentoo.org>
-Ciaran McCreesh <ciaranm@gentoo.org>
-.fi
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/check-reqs.eclass.5,v 1.1.2.3 2005/05/10 11:30:32 swegener Exp $
+++ /dev/null
-.TH CVS.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-cvs.eclass \- provides generic cvs fetching functions
-.SH DESCRIPTION
-The \fBcvs\fR eclass contains a suite of functions that are used to
-create 'live' cvs ebuilds. These ebuilds are called 'live' because
-they will checkout a cvs repository at the time of emerge and compile
-the source from the checkout. This eclass usually generates pretty
-unstable ebuilds ... but you can't get anymore bleeding edge than
-a live cvs checkout :).
-
-Common usage of this eclass involves setting \fBECVS_SERVER\fR and
-\fBECVS_MODULE\fR to grab the relevant cvs sources, and then letting
-the eclass define \fBsrc_unpack\fR for you.
-.SH VARIABLES
-.TP
-.B "ECVS_CVS_COMMAND" = \fI"cvs -q -f -z4"\fR
-The command to run in order to checkout the module from the cvs
-repository. You should not need to change this.
-.TP
-.B "ECVS_UP_OPTS" = \fI"-dP"\fR
-Options to pass to \fBECVS_CVS_COMMAND\fR when running an update.
-You should not have to modify this.
-.TP
-.B "ECVS_CO_OPTS" = \fI""\fR
-Options to pass to \fBECVS_CVS_COMMAND\fR when running a checkout.
-You should not have to modify this.
-.TP
-.B "ECVS_TOP_DIR" = \fI"${DISTDIR}/cvs-src"\fR
-Where the cvs modules will be stored and then accessed. You
-should not have to modify this.
-.TP
-.B "ECVS_SERVER" = \fI"offline"\fR
-Set this to the server that you will be checking the sources out of.
-If you set this to 'offline' then the eclass will assume the module
-is already checked out and in \fBECVS_TOP_DIR\fR. You almost always
-will set this variable.
-.TP
-.B "ECVS_AUTH" = \fI"pserver"\fR
-The authentication method to use to checkout the sources. Please
-note that the only method currently supported is 'pserver'. You
-should not need to modify this variable.
-.TP
-.B "ECVS_USER" = \fI"anonymous"\fR
-The user to log into the server with.
-.TP
-.B "ECVS_PASS" = \fI""\fR
-The password to log into the server with.
-.TP
-.B "ECVS_MODULE" = \fI""\fR
-The module to checkout from the cvs server. Please note that you
-*must* set this variable.
-.TP
-.B "ECVS_BRANCH" = \fI"HEAD"\fR
-The branch to checkout the sources from. The common targets are
-HEAD (current 'stable' cvs code) and SPLIT (current 'unstable' cvs
-code).
-.SH FUNCTIONS
-.TP
-.B cvs_fetch
-This function will setup \fBECVS_TOP_DIR\fR and any other pre-checkout
-steps that may need to be taken. Then it will login into the server
-and finally checkout the sources from cvs. You usually do not call
-this function yourself, but rather let it be handled by \fBcvs_src_unpack\fR.
-.TP
-.B cvs_src_unpack
-This function will determine where the cvs files need to be saved and
-then where they need to be placed after the checkout. The final result
-is that you will have a copy of \fBECVS_MODULE\fR in \fB${WORKDIR}\fR. Thus
-you will usually set \fB${S}\fR to be \fB${WORKDIR}/${ECVS_MODULE}\fR.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/cvs.eclass
-.SH AUTHORS
-Mike Frysinger <vapier@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/cvs.eclass.5,v 1.4.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "DISTUTILS.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-distutils.eclass \- allow easier installation of distutils-based python modules
-.SH "DESCRIPTION"
-The \fBdistutils\fR eclass is designed to allow easier installation of
-distutils-based python modules and their incorporation into the Gentoo
-Linux system. The eclass defines \fBsrc_compile\fR and \fBsrc_install\fR
-for you. You should be able to make a quick ebuild without setting up
-any extra variables or functions.
-.SH "VARIABLES"
-.TP
-.B PYTHON_SLOT_VERSION = \fI"[0|2.1]"\fR
-This allows you to depend on python-2.1. This is usually only
-needed by a -py21- ebuild. Otherwise you should not have to set this.
-.TP
-.B DOCS = \fI"<files to give to dodoc>"\fR
-This will cause \fBsrc_install\fR to install a few extra documentation
-files than normal.
-.SH "FUNCTIONS"
-.TP
-.B distutils_python_version
-This will setup the variables \fBPYVER_MAJOR\fR, \fBPYVER_MINOR\fR,
-and \fBPYVER\fR with the corresponding values of the python version.
-.TP
-.B distutils_python_tkinter
-If the package requires tkinter support, then calling this function
-will cause the ebuild to fail if tkinter support does not exist. An
-informative message will be displayed telling the user they need to
-recompile python with tkinter support for the ebuild to emerge.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/distutils.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/distutils.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "EBOOK.ECLASS" "5" "Aug 2004" "Portage 2.0.51" "portage"
-.SH "NAME"
-ebook.eclass \- easy installation of ebooks
-.SH "DESCRIPTION"
-The \fBebook\fR eclass makes writing ebuilds for ebooks a trivial task.
-.SH "VARIABLES"
-\fINOTE\fR: the following variables should be set \fBBEFORE\fR inheriting the
-\fBebook\fR eclass:
-.TP
-.BR "DESCRIPTION"
-Package description. Defaults to "\fB${P}\fR ebook based on ebook eclass".
-.TP
-.BR "RDEPEND"
-Run-time dependencies. Defaults to ">=dev-util/devhelp-0.6".
-.TP
-.BR "EBOOKNAME"
-The name of the ebook. This variable \fImust\fR be set.
-.TP
-.BR "EBOOKVERSION"
-The version of the ebook. This variable \fImust\fR be set, even if there is
-no version. See the \fB${NOVERSION}\fR variable below for more information.
-.TP
-.BR "SRC"
-The name of the file to download, minus the file extension. This variable
-defaults to \fB${EBOOKNAME}\fR-\fB${EBOOKVERSION}\fR.
-.TP
-.BR "SRC_URI"
-The ebook URI to download. Defaults to "http://lidn.sourceforge.net/books_download/\fB${SRC}\fR.\fB${EBOOKEXT}\fR".
-.TP
-.BR "EBOOKEXT"
-The file name extension of \fB${SRC}\fR. Defaults to tar.gz.
-.TP
-.BR "EBOOKDESTDIR"
-The directory inside \fB${DEVHELPROOT}\fR/books/\fB${EBOOKDIR}\fR in which the
-ebook will be installed. This variable defaults to \fB${EBOOKNAME}\fR-\fB${EBOOKVERSION}\fR
-or \fB${EBOOKNAME}\fR if the \fB${NOVERSION}\fR variable is set.
-.TP
-.BR "EBOOKFROMDIR"
-The directory in which the ebook's HTML files are located after unpacking
-\fB${SRC_URI}\fR. This directory is relative to \fB${WORKDIR}\fR. This
-variable defaults to \fB${EBOOKNAME}\fR-\fB${EBOOKVERSION}\fR or \fB${EBOOKNAME}\fR
-if the \fB${NOVERSION}\fR variable is set.
-.TP
-.BR "BOOKDEVHELPFILE"
-The file name that the ebook's book.devhelp will be installed as. This variable
-defaults to \fB${EBOOKNAME}\fR-\fB${EBOOKVERSION}\fR.devhelp or \fB${EBOOKNAME}\fR.devhelp
-if the \fB${NOVERSION}\fR variable is set.
-.TP
-.BR "BOOKDESTDIR"
-The directory in which the ebook's HTML will be installed into. Defaults to
-\fB${EBOOKNAME}\fR-\fB${EBOOKVERSION}\fR or \fB${EBOOKNAME}\fR is the \fB${NOVERSION}\fR
-variable is set.
-.TP
-.BR "NOVERSION"
-If this variable is not empty, all instances of \fB${EBOOKVERSION}\fR will be
-removed from all variables.
-.TP
-.BR "DEVHELPROOT"
-The location of devhelp's data directory. Defaults to usr/share/devhelp.
-.SH "FUNCTIONS"
-\fINOTE\fR: the following functions will be used as the defaults should they
-be omitted from the ebuild.
-.TP
-.BR "ebook_src_install"
-Installs \fB${BOOKDEVHELPFILE}\fR and all HTML files into \fB${DEVHELPROOT}\fR/books/\fB${EBOOKDESTDIR}\fR.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/ebook.eclass
-.SH "AUTHORS"
-Aaron Walker <ka0ttic@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/ebook.eclass.5,v 1.2.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "EUTILS.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-eutils.eclass \- many extra (but common) functions that are used in ebuilds
-.SH "DESCRIPTION"
-The \fBeutils\fR eclass contains a suite of functions that complement
-the ones that ebuild.sh already contain. The idea is that the functions
-are not required in all ebuilds but enough utilize them to have a common
-home.
-.SH "FUNCTIONS"
-.TP
-.BR "cdrom_get_cds " "\fI<cd1 file>\fR \fI[cd2 file]\fR \fI[cd n file]\fR"
-Useful function to help ebuilds that need to read files off of a CD. This is
-most commonly used with games. Just specify a list of files, one per cd, that
-will be used to detect whether the cd is mounted or not. This function
-handles all the messy details of interaction with the user. Once this
-function returns, you will have access to the \fICDROM_ROOT\fR variable. If
-you want the message to the user to name the CD in a particular way, then
-export the variable \fICDROM_NAME\fR before calling this function. If you want
-to name more than one cd, and you want them to each have a different name, then
-export the variables \fICDROM_NAME_1\fR, \fICDROM_NAME_2\fR, etc... For more
-information on multi-cd support, see \fBcdrom_load_next_cd\fR.
-.TP
-.BR "cdrom_load_next_cd"
-Some packages are so big they come on multiple CDs. When you're done reading
-files off a CD and want access to the next one, just call this function. Again,
-all the messy details of user interaction are taken care of for you. Once this
-returns, just read the variable \fICDROM_ROOT\fR for the location of the mounted
-CD. Note that you can only go forward in the CD list, so make sure you only
-call this function when you're done using the current CD.
-.TP
-.BR "draw_line"
-Simple function to draw a line consisting of '=' the same length as $*. So
-if you run `draw_line 1234 5678` you will get back 9 '=' characters in a line.
-.TP
-.BR "edos2unix " "\fI<files>\fR"
-A handy replacement for dos2unix, recode, fixdos, etc... This allows you
-to remove all of these text utilities from DEPEND variables because this
-is a script based solution. Just give it a list of files to convert and
-they will all be changed from the DOS CRLF format to the UNIX LF format.
-.TP
-.BR "enewgroup " "\fI<group>\fR \fI[gid]\fR"
-This function does not require you to understand how to properly add a
-group to the system. Just give it a \fIgroup name\fR to add and \fBenewgroup\fR will
-do the rest. You may specify the \fIgid\fR for the group or allow the group to
-allocate the next available one.
-.TP
-.BR "enewuser " "\fI<user>\fR \fI[uid]\fR \fI[shell]\fR \fI[homedir]\fR \fI[groups]\fR \fI[params]\fR"
-Same as \fBenewgroup\fR, you are not required to understand how to properly add
-a user to the system. The only required parameter is the \fIusername\fR.
-.br
-.BR "Default Values"
-.br
-\fIuid\fR: next available (pass -1 to get default behavior)
-.br
-\fIshell\fR: /bin/false
-.br
-\fIhomedir\fR: /dev/null
-.br
-\fIgroups\fR: no groups
-.br
-\fIparams\fR: any other parameters \fBuseradd\fR(8) accepts; see the manpage for more details
-.TP
-.BR "epatch"
-See the section on \fBepatch\fR below.
-.TP
-.BR "gen_usr_ldscript"
-Generate linker scripts in /usr/lib for dynamic libs in /lib. This is to fix linking
-problems when you have the .so in /lib, and the .a in /usr/lib. What happens is that
-in some cases when linking dynamic, the .a in /usr/lib is used instead of the .so in
-/lib due to gcc/libtool tweaking ld's library search path.
-.TP
-.BR "get_number_of_jobs"
-Checks how many cpu's are present in the system and then sets -j in MAKEOPTS accordingly.
-.TP
-.BR "have_NPTL"
-This function return true if we are using the NPTL pthreads implementation of glibc.
-.TP
-.BR "make_desktop_entry " "\fI<binary>\fR \fI[name]\fR \fI[icon]\fR \fI[type]\fR \fI[path]\fR"
-Make a little shortcut in GNOME/KDE menus for your application. Just pass the name
-of the binary to execute and the rest will be done for you. If you want to change
-the name that will show up in the menu, pass the function a \fIname\fR parameter. If you
-want to specify an \fIicon\fR (default is \fB${PN}\fR.png) then pass a name of a graphic file
-relative to /usr/share/pixmaps/ or the full path to a file. If you want to specify the
-section of the menu that the icon will install to (rather than the default determined
-by \fB${CATEGORY}\fR) then pass a \fItype\fR value (see http://www.freedesktop.org/standards/menu-spec/
-for valid values). Finally, if the application needs to start up in a special directory,
-pass the last value as the full \fIpath\fR name.
-.TP
-.BR "unpack_makeself " "\fI[makeself archive]\fR \fI[byte offset]\fR"
-Unpack a makeself archive rather than relying on the script to unpack itself. Useful for when
-the scripts use old (POSIX) syntax that is no longer supported properly. If you don't specify
-a file to unpack, then \fB${A}\fR is used instead. If you don't specify the offset, then the
-proper value will be located by searching the makeself script.
-For more information on makeself archives, please visit: http://www.megastep.org/makeself/
-.TP
-.BR "unpack_pdv " "\fI<pdv archive>\fR \fI<sizeof(off_t)>\fR"
-Unpack a pdv archive rather than relying on the binary to unpack itself. Useful for when
-the static binary crashes randomly on systems and for when the binary doesn't provide a
-non-interactive extraction process. You have to specify the off_t size since I (vapier@gentoo.org)
-am unaware of a way to extract that information out of the binary executable automatically.
-The value you pass is the size of the off_t type (in bytes) on the machine that built the
-pdv archive. If you don't know the value yourself, try guessing the values 2, 4, or 8.
-For more information on pdv archives, please visit: http://pdv.sourceforge.net/
-.SH "EPATCH"
-.TP
-.B "ABOUT"
-\fBepatch\fR is designed to make patching easy. It does all the common checks that
-a developer would do with the \fBpatch\fR(1) command and then some. It will attempt
-to apply the patch for a range of offset values (-p0 to -p5, all relative to the working
-directory when \fBepatch\fR was called). If the patch fails to apply (by testing via
-dryruns), then \fBpatch\fR will stop the emerge process by calling \fBdie\fR. You will
-be given a log file of the output of the patch attempt so as to ease debugging. The
-output of a successful patch is a pretty formatted message showing what patches were
-applied. \fBepatch\fR can be used for bulk patching or for just one or two patches.
-Additionally, it can handle patches in bzip2, gzip, compress (Z), and zip formats.
-.TP
-.B "USAGE"
-.RS
-.TP
-.B "epatch " "\fI<patch file>\fR"
-The most common and easiest way to use \fBepatch\fR is by just giving it the full path
-to a patch file.
-.TP
-.B "epatch " "\fI<directory>\fR"
-A more powerful use is to fill a directory with patches and then let \fBepatch\fR apply
-all the patches inside it. The patches must be in the format ??_${\fBARCH\fR}_foo.${\fBEPATCH_SUFFIX\fR}.
-This ensures that there are a set order, and you can have \fBARCH\fR specific patches.
-
-.br
-01_all_misc-fix.patch.bz2
-.br
- apply the misc-fix patch first for all arches
-.br
-02_sparc_another-fix.patch.bz2
-.br
- apply the another-fix patch second but only on sparc
-.RE
-.TP
-.B VARIABLES
-.RS
-.TP
-.B "EPATCH_SOURCE" = \fI"${WORKDIR}/patch"\fR
-The patch or directory of patches for \fBepatch\fR to apply. This is set
-automatically if you call \fBepatch\fR with a parameter.
-.TP
-.B "EPATCH_SUFFIX" = \fI"patch.bz2"\fR
-When applying bulk patches this is the suffix that all patches will have.
-.TP
-.B "EPATCH_OPTS" = \fI""\fR
-Any extra options you may want to pass to \fBpatch\fR(1). We can't think
-of everything so why restrict you :). The default is "" of course.
-.TP
-.B "EPATCH_EXCLUDE" = \fI""\fR
-A space delimited list (well, actually \fB$IFS\fR delimited ...) of patch
-files to skip while bulk patching. Use only file names, not full paths.
-.TP
-.B "EPATCH_SINGLE_MSG" = \fI"Applying <patch name>"\fR
-If you only apply a single patch, then instead of displaying the default
-message you can change it to say anything you want, even 'Dont call me Radio Unit 51',
-if you are so inclined of course.
-.TP
-.B "EPATCH_FORCE" = \fI"[yes|no]"\fR
-This allows you to apply all patches in \fBEPATCH_SOURCE\fR even if they
-dont match the ??_${\fBARCH\fR}_foo.${\fBEPATCH_SUFFIX\fR} file naming
-convention. By default we want you to use the above convention.
-.RE
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/eutils.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/eutils.eclass.5,v 1.5.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "FIXHEADTAILS.ECLASS" "5" "Aug 2004" "Portage 2.0.51" "portage"
-.SH "NAME"
-fixheadtails.eclass \- functions for replacing obsolete head/tail invocations
-with newer POSIX compliant ones.
-.SH "DESCRIPTION"
-The \fBfixheadtails\fR eclass contains functions for parsing file(s) and
-replacing obsolete head/tail invocations in the form similar to:
-.TP
-head -# <file>
-.TP
-with the newer POSIX compliant form of:
-.TP
-head -n# <file>
-.SH "FUNCTIONS"
-\fBNOTE\fR: these functions are usually used in the \fIsrc_unpack\fR function.
-.TP
-.BR "ht_fix_file " "\fI<file1> [file2] [file3] [...]\fR"
-Fixes head/tail invocations in specific files.
-.TP
-.BR "ht_fix_all"
-Scans the current directory (recursively), calling \fBht_fix_file\fR for each
-file that contains an obsolete head/tail invocation.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/fixheadtails.eclass
-.SH "AUTHORS"
-Aaron Walker <ka0ttic@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/fixheadtails.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "FLAG-O-MATIC.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-flag\-o\-matic.eclass \- manipulate CFLAGS/CXXFLAGS easily and reliably
-.SH "DESCRIPTION"
-The \fBflag\-o\-matic\fR eclass contains a suite of functions to
-manipulate the CFLAGS/CXXFLAGS variables.
-.SH "FUNCTIONS"
-.TP
-.BR "append-flags " "\fI<flags>\fR"
-Add extra \fIflags\fR to the current CFLAGS/CXXFLAGS.
-.TP
-.BR "filter-flags " "\fI<flags>\fR"
-Remove particular \fIflags\fR from CFLAGS/CXXFLAGS. This function
-will only match complete flags.
-.TP
-.BR "replace-flags " "\fI<orig-flag>\fR \fI<new-flag>\fR"
-Replace all occurences of \fIoriginal flag\fR with \fInew flag\fR.
-.TP
-.BR "replace-cpu-flags " "\fI<old cpus>\fR \fI<new cpu>\fR"
-Replace all -march, -mcpu, and -mtune flags which contain \fIold cpus\fR
-with -march, -mcpu, and -mtune flags which contain \fInew cpu\fR.
-.TP
-.BR "get-flag " "\fI<flag>\fR"
-If \fIflag\fR is prefixed with -, then the whole flag will
-be echoed. If just the flag name is specified, and the flag has
-a setting, the value for the flag will be echoed instead.
-
-.I Examples:
-.br
-CFLAGS="-march=i586 -ffast-math"
-.br
-`get-flag -march` == "-march=i586"
-.br
-`get-flag march` == "i586"
-.br
-`get-flag -ffast-math` == "-ffast-math"
-.br
-`get-flag ffast-math` == "-ffast-math"
-.TP
-.BR "is-flag " "\fI<flag>\fR"
-Returns true if \fIflag\fR is in CFLAGS or CXXFLAGS.
-.TP
-.BR "filter-mfpmath " "\fI<math types>\fR"
-Remove specified \fImath types\fR from the selected fpmath units.
-If the user has -mfpmath=sse,386, running `filter-mfpmath sse`
-will leave the user with -mfpmath=386.
-.TP
-.BR "append-ldflags " "\fI<flags>\fR"
-Add extra \fIflags\fR to the current LDFLAGS.
-.TP
-.BR "filter-ldflags " "\fI<flags>\fR"
-Remove particular \fIflags\fR from LDFLAGS. This function
-will only match complete flags.
-.TP
-.BR "filter-lfs-flags"
-Remove flags that enable Large File Support.
-.TP
-.BR "append-lfs-flags"
-Add flags that enable Large File Support.
-.TP
-.BR "strip-flags"
-Strip CFLAGS/CXXFLAGS of everything except for flags known to
-be good flags, or are flags that affect the ABI. Users of stable
-profile are limited to these flags:
-.br
-.I "-O -O1 -O2 -mcpu -march -mtune -fstack-protector -pipe -g"
-.br
-Users of unstable profile are allowed the above flags and these flags:
-.br
-.I "-Os -O3 -freorder-blocks -fprefetch-loop-arrays"
-.TP
-.BR "test_flag " "\fI<flag>\fR"
-Tests to see if \fIflag\fR is supported by the active toolchain.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5),
-.BR make.conf (5)
-.SH "FILES"
-.BR /usr/portage/eclass/flag\-o\-matic.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/flag-o-matic.eclass.5,v 1.5.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "FONT.ECLASS" "5" "Aug 2004" "Portage 2.0.51" "portage"
-.SH "NAME"
-font.eclass \- easy, uniform font installation
-.SH "DESCRIPTION"
-The \fBfont\fR eclass attempts to make font installation as easy as possible.
-Everything that usually involves installing fonts (such as creating scalable
-font indecis, updating the font cache, etc...) is transparently taken
-care of by the \fBfont\fR eclass.
-.SH "EXAMPLES"
-Here's a simple example ebuild:
-.nf
-inherit font
-
-DESCRIPTION="a collection of fonts for Nepali users"
-HOMEPAGE="http://www.mpp.org.np/"
-SRC_URI="mirror://gentoo/${P}.tar.bz2"
-
-LICENSE="freedist"
-SLOT="0"
-KEYWORDS="alpha amd64 ppc x86"
-IUSE=""
-
-DEPEND=""
-
-S="${WORKDIR}/${PN}"
-FONT_S=${S}
-FONT_SUFFIX="ttf"
-.fi
-.SH "VARIABLES"
-.TP
-.B "FONT_SUFFIX"
-Space-delimited list of font suffixes to install.
-.TP
-.B "FONT_S"
-Directory containing the fonts. If omitted, \fB${S}\fR will be used.
-.TP
-.B "DOCS"
-Space-delimited list of documents to install.
-.SH "FUNCTIONS"
-.TP
-.B "font_xfont_config"
-Creates font indecis for X font files and also installs a fonts.alias file,
-if it exists. This function is called by \fIfont_src_install\fR.
-.TP
-.B "font_xft_config"
-Creates fontconfig cache. This function is also called by \fIfont_src_install\fR.
-.TP
-.B "font_src_install"
-Installs all fonts ending with suffixes listed in \fB${FONT_SUFFIX}\fR as well
-as any documents listed in \fB${DOCS}\fR. This function will be used as the
-default \fIsrc_install\fR function in an ebuild that omits one.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/font.eclass
-.SH "AUTHORS"
-.nf
-Aaron Walker <ka0ttic@gentoo.org>
-Mike Frysinger <vapier@gentoo.org>
-.fi
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/font.eclass.5,v 1.2.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH FORTRAN.ECLASS 5 "Nov 2004" "Portage 2.0.51" "portage"
-.SH NAME
-fortran.eclass \- functions for fortran packages
-.SH DESCRIPTION
-The \fBfortran\fR eclass provides an interface to ease the integration of the
-various fortran compilers available.
-.SH VARIABLES
-\fBNOTE\fR: since the \fBfortran\fR eclass does not check to see if the
-following variables are set prior to inheritance, you must ensure that if you
-need to define any of them, that you do so after inheritance occurs.
-.TP
-.B FORTRAN
-Defines a list of fortran compilers that can be used for the build. Defaults
-to 'f77'.
-.TP
-.B f77_CONF
-Defines configure option that enables the use of the f77 compiler. Defaults
-to '--with-f77'.
-.TP
-.B f2c_CONF
-Defines configure option that enables the use of the f2c compiler. Defaults
-to '--with-f2c'.
-.SH FUNCTIONS
-.TP
-.B fortran_conf
-Displays the necessary configure options for the currently selected fortran
-compiler.
-.TP
-.B need_fortran \fI[ profile1 ] < profile2 >\fR
-Checks to see if at least one of the specified profiles is installed. Currently
-supported profiles include \fBf77\fR, \fBf2c\fR, and \fBifc\fR.
-.TP
-.B patch_fortran
-Applies any patches located in \fB${FILESDIR}\fR named "\fB${P}\fR-COMPILER*",
-where COMPILER is the fortran compiler currently selected for use.
-.TP
-.B fortran_pkg_setup
-Default pkg_setup which calls \fBneed_fortran\fR to ensure that a suitable
-fortran compiler is installed.
-.TP
-.B fortran_src_unpack
-Default src_unpack which besides unpacking the distfile(s), calls
-\fBpatch_fortran\fR to apply any compiler-specific patches.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/fortran.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/fortran.eclass.5,v 1.1.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "GAMES.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-games.eclass \- standardize the install of all games
-.SH "DESCRIPTION"
-The \fBgames\fR eclass is used to centrally control how all games
-will be emerged onto systems. Here we basically control the filesystem
-locations and the ownership of all files. If you want to change an
-aspect of how your games are installed, then just edit the \fBgames\fR
-eclass ! :)
-.SH "VARIABLES"
-.TP
-.B "GAMES_PREFIX" = \fI"/usr/games"\fR
-The prefix that the game will be installed under.
-.TP
-.B "GAMES_PREFIX_OPT" = \fI"/opt"\fR
-The prefix that the game will be installed under if it is a binary distribution.
-.TP
-.B "GAMES_DATADIR" = \fI"/usr/share/games"\fR
-The prefix for installing shared data files.
-.TP
-.B "GAMES_DATADIR_BASE" = \fI"/usr/share"\fR
-Same as above, but some games auto append '/games/' to the datadir path.
-.TP
-.B "GAMES_SYSCONFDIR" = \fI"/etc/games"\fR
-The location where games will save their configuration files.
-.TP
-.B "GAMES_STATEDIR" = \fI"/var/games"\fR
-The location where games will save their state in behind runs. This
-includes things like highscore files. If a game creates more than
-one file, have it save all files inside \fB${GAMES_STATEDIR}/${PN}\fR.
-Otherwise, just create the single file in \fB${GAMES_STATEDIR}/\fR.
-Again, try to use a package specific name for the file if you are
-creating it directly in the statedir.
-.TP
-.B "GAMES_LIBDIR" = \fI"/usr/games/lib"\fR
-The location where games will store their libraries.
-.TP
-.B "GAMES_BINDIR" = \fI"/usr/games/bin"\fR
-The location where the games will store/link their executables. Putting
-game binaries here helps to cut down on the $PATH bloat.
-.TP
-.B "GAMES_ENVD" = \fI"90games"\fR
-The filename that the env.d entry will use.
-.TP
-.B "GAMES_USER" = \fI"games"\fR
-The user that will own all game related files.
-.TP
-.B "GAMES_GROUP" = \fI"games"\fR
-The group that will own all game related files.
-.SH "FUNCTIONS: general"
-.TP
-.B "prepgamesdirs" \fI[directories]\fR
-This will change ownership on all files/directories found inside of
-the \fBGAMES_*\fR variables and any extra directories specified as
-parameters. It will change the permissions on all directories to
-750 (u+rwx,g+rx-w,u-rwx) and change the permissions of all files
-with a mask of g+r,o-rwx.
-.br
-\fB*NOTE\fR: This should *always* be the last thing called in the
-\fBsrc_install\fR function. If portage allowed for hookable calls then
-this would be hooked to the end of \fBsrc_install\fR, but until that
-happens, make sure to call!
-.TP
-.B games_pkg_setup
-This will automagically add \fBGAMES_USER\fR and \fBGAMES_GROUP\fR to
-your system. If you define \fBpkg_setup\fR in your ebuild, then make
-sure to call this function at the end of the function.
-.TP
-.B games_pkg_postinst
-This will automagically generate the \fBGAMES_ENVD\fR file and display
-a little message about being in the \fBGAMES_GROUP\fR in order to play
-a game. If you define \fBpkg_postinst\fR in your ebuild, then make
-sure to call this function at the end of the function.
-.SH "FUNCTIONS: compile"
-.TP
-.B egamesconf
-The same as \fBeconf\fR except this passes all the game related variables
-(see above). For more info on \fBeconf\fR see \fBebuild\fR(5).
-.SH "FUNCTIONS: install"
-.TP
-.B egamesinstall
-The same as \fBeinstall\fR except this passes all the game related variables
-(see above). For more info on \fBeinstall\fR see \fBebuild\fR(5).
-.TP
-.B dogamesbin dogamessbin
-The same as \fBdobin\fR and \fBdosbin\fR respectively except these will
-install binaries into \fBGAMES_PREFIX\fR. For more info see \fBebuild\fR(5).
-.TP
-.B dogameslib dogameslib.a dogameslib.so
-The same as \fBdolib\fR, \fBdolib.a\fR, and \fBdolib.so\fR respectively
-except these will install binaries into \fBGAMES_PREFIX\fR. For more info
-see \fBebuild\fR(5).
-.TP
-.B newgamesbin newgamessbin
-The same as \fBnewbin\fR and \fBnewsbin\fR respectively except these will
-install binaries into \fBGAMES_PREFIX\fR. For more info see \fBebuild\fR(5).
-.TP
-.B gamesowners \fI<files/directories>\fR
-\fBgamesowners\fR will change the user and group ownership to \fBGAMES_USER\fR
-and \fBGAMES_GROUP\fR respectively.
-.TP
-.B gamesperms \fI<files/directories>\fR
-\fBgamesperms\fR will change the permissions with a mask of u+rw,g+r-w,o-rwx.
-.TP
-.B games_make_wrapper \fI<wrapper>\fR \fI<bin>\fR \fI<chdir>\fR
-Create a small wrapper script. Useful when dealing with packages that need to
-change directory to the base of their data tree before running. This will create
-a wrapper script called \fIwrapper\fR that will chdir to \fIchdir\fR before
-executing \fIbin\fR. The \fIwrapper\fR will be placed in \fBGAMES_BINDIR\fR.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/games.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/games.eclass.5,v 1.7.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "HORDE.ECLASS" "5" "Aug 2004" "Portage 2.0.51" "portage"
-.SH "NAME"
-horde.eclass \- standardize the installation of horde packages
-.SH "DESCRIPTION"
-The \fBhorde\fR eclass provides generic functions to make the writing of
-horde ebuilds trivial. The \fBhorde\fR eclass also provides transparent
-support for live CVS ebuilds via the \fBcvs.eclass\fR(5) (when \fB${PN}\fR
-contains "-cvs").
-.SH "VARIABLES"
-.BR "HORDE_PHP_FEATURES"
-A whitespace-delimited list of mod_php USE flags. If set,
-\fIhorde_pkg_setup\fR will check to make sure that mod_php was compiled with
-the specified USE flags. If not, the build will fail, notifying the user that
-they must rebuild mod_php with the specified USE flags.
-.SH "FUNCTIONS"
-.TP
-.BR "horde_pkg_setup"
-Handles the nasty details of the \fBwebapp.eclass\fR(5) and checks
-\fIHORDE_PHP_FEATURES\fR, if set.
-.TP
-.BR "horde_src_unpack"
-In the case of a live CVS ebuild, this function calls \fIcvs_src_unpack\fR
-from the \fBcvs\fR eclass. Otherwise, \fIunpack\fR is called.
-.TP
-.BR "horde_src_install"
-Installs all files in \fB${S}\fR into the \fBwebapp\fR eclass'
-\fB${MY_HTDOCSDIR}\fR directory. This will also installs documentation
-(the README and all files in in \fB${S}/docs/\fR). Then the rest of the
-nasty details of the \fBwebapp.eclass\fR(5) are taken care of.
-.TP
-.BR "horde_pkg_postinst"
-Displays various informational and/or warning messages.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5),
-.BR cvs.eclass (5),
-.BR webapp.eclass (5)
-.SH "FILES"
-.nf
-.BR /usr/portage/eclass/horde.eclass
-.BR /usr/portage/eclass/webapp.eclass
-.BR /usr/portage/eclass/cvs.eclass
-.fi
-.SH "AUTHORS"
-.nf
-Aaron Walker <ka0ttic@gentoo.org>
-Mike Frysinger <vapier@gentoo.org>
-.fi
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/horde.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "LIBTOOL.ECLASS" "5" "Aug 2004" "Portage 2.0.51" "portage"
-.SH "NAME"
-libtool.eclass \- fixes the libtool files that are distributed with some
-packages
-.SH "DESCRIPTION"
-The \fBlibtool\fR eclass provides an easy way to patch the libtool files
-that come with some packages. Often times these files are outdated and
-misbehave inside of the portage build environment.
-.SH "VARIABLES"
-.BR "ELT_APPLIED_PATCHES"
-This variable is exported by the \fBlibtool\fR eclass. It contains a
-whitespace-delimited list of patches that were successfully applied.
-.SH "FUNCTIONS"
-.TP
-.B "elibtoolize " "\fI[--portage] [--reverse-deps] [--patch-only] [--remove-internal-dep=DEP_TO_REMOVE] [--shallow]\fR"
-This function should be called from \fIsrc_unpack\fR. If called with no
-arguments, it will apply a default set of patches to all occurrences of
-ltmain.sh and then run libtoolize. The default set of patches are located
-in \fB${PORTDIR}\fR/eclass/ELT-patches.
-.RS
-.TP
-.BR "--portage"
-Apply the portage patch.
-.TP
-.BR "--reverse-deps"
-Apply the reverse dependencies patch. See http://bugzilla.gnome.org/show_bug.cgi?id=75635
-for more information.
-.TP
-.BR "--patch-only"
-If specified, libtoolize will not be run if none of the patches apply.
-.TP
-.BR "--remove-internal-deps=DEP_TO_REMOVE"
-Replaces @REM_INT_DEP@ with DEP_TO_REMOVE.
-.TP
-.BR "--shallow"
-Instead of recursively patching all occurrences of ltmain.sh, only patch the
-ltmain.sh in \fB${S}\fR.
-.RE
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/libtool.eclass
-.SH "AUTHORS"
-Aaron Walker <ka0ttic@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/libtool.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "PERL-MODULE.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-perl-module.eclass \- handles generic perl module ebuilds
-.SH "DESCRIPTION"
-The \fBperl-module\fR eclass is used for the compilation, testing, and
-installation of perl modules within the portage system, following
-vanilla procedure for modules using either \fBExtUtils::MakeMaker\fR(3pm)
-or \fBModule::Builder\fR(3pm).
-.SH "VARIABLES"
-.TP
-.B "style" = \fI"[builder|makemaker]"\fR
-This variable allows you to choose which package to use as the default
-for building the module. If you do not specify a \fIstyle\fR, then
-the default \fBExtUtils::MakeMaker\fR(3pm) will be used.
-.SH "FUNCTIONS"
-.TP
-.B perl-module_src_prep
-Create the initial Makefile.
-.TP
-.B perl-module_src_compile
-Calls \fBperl-module_src_prep\fR if it hasn't been already. Runs
-initial make.
-.TP
-.B perl-module_src_test
-If invoked, runs all the tests distributed with the module.
-.TP
-.B perl-module_src_install
-Runs `make install` (or the \fBModule::Builder\fR(3pm) equivelant if it
-is a builder module). Also cleans build paths from pod files and
-generated perllocal.pod.
-.TP
-.B perl-module_pkg_setup
-Calls \fBperlinfo\fR.
-.TP
-.B perl-module_pkg_preinst
-Calls \fBperlinfo\fR.
-.TP
-.B perl-module_pkg_postinst
-Calls \fBupdatepod\fR.
-.TP
-.B perl-module_pkg_prerm
-Calls \fBupdatepod\fR.
-.TP
-.B perl-module_pkg_postrm
-Calls \fBupdatepod\fR.
-.TP
-.B perlinfo
-Updates the gentoo-pods documentation.
-.TP
-.B updatepod
-Cleans the perllocal.pods in ARCH_LIB and SITE_LIB.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5),
-.BR ExtUtils::MakeMaker (3pm),
-.BR Module::Build (3pm),
-.BR perl (1)
-.SH "FILES"
-.BR /usr/portage/eclass/perl-module.eclass
-.SH "AUTHORS"
-Michael Cummings <mcummings@gentoo.org>
-.br
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/perl-module.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH PYTHON.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-python.eclass \- functions for Python-related ebuilds
-.SH DESCRIPTION
-The \fBpython\fR eclass provides general utility functions for Python-related
-ebuilds.
-.SH VARIABLES
-.TP
-.B PYVER
-Defines major and minor Python version. This is a READ-ONLY variable, set by
-the \fBpython_version\fR function.
-.TP
-.B PYVER_MAJOR
-Defines major Python version. This is a READ-ONLY variable, set by the
-\fBpython_version\fR function.
-.TP
-.B PYVER_MINOR
-Defines minor Python version. This is a READ-ONLY variable, set by the
-\fBpython_version\fR function.
-.TP
-.B PYVER_MICRO
-Defines micro Python version. This is a READ-ONLY variable, set by the
-\fBpython_version\fR function.
-.TP
-.B PYTHON_OVERRIDE_PYVER = \fI"2.2"\fR
-When set, overrides the version of Python to use in the \fBpython_mod_compile\fR
-and \fBpython_mod_optimize\fR functions.
-.SH FUNCTIONS
-.TP
-.B python_version
-Sets variables \fBPYVER\fR, \fBPYVER_MAJOR\fR, \fBPYVER_MINOR\fR, and
-\fBPYVER_MICRO\fR to the version of Python currently available.
-.TP
-.B python_disable_pyc
-Disables automatic recompilation of modules to .pyc/.pyo. This is supported by
->=dev-lang/python-2.2.3-r3 only.
-.TP
-.B python_enable_pyc
-Enables automatic recompilation of modules to .pyc/.pyo. This is supported by
->=dev-lang/python-2.2.3-r2 only.
-.TP
-.B python_makesym
-Creates the /usr/bin/python symbolic link to point to the latest installed
-version of Python.
-.TP
-.B python_tkinter_exists
-Checks to see if Python was compiled with Tkinter support (via USE=tcltk).
-If not, this function will print an error message informing the user that
-Tkinter support is required and then die.
-.TP
-.B python_mod_exists \fI[ module ]\fR
-Checks to see if the specified module is installed and loadable. Returns true
-(0) if so or false (1) if not.
-.TP
-.B python_mod_compile \fI[ file ]\fR
-Precompiles the specified file, creating the module's pyc and pyo files. If
-the variable, \fBPYTHON_OVERRIDE_PYVER\fR is set, this function will use the
-specified version of Python to compile rather than the version detected by
-\fBpython_version\fR. This function should only be run from \fBpkg_postinst\fR.
-.TP
-.B python_mod_optimize \fI< dir1 > < dir 2 >\fR
-If called with no arguments, this function will recompile all modules under
-sys.path without recursing into subdirectories. Called with arguments, this
-function will recursively compile all modules in the specified directories.
-If the variable, \fBPYTHON_OVERRIDE_PYVER\fR is set, this function will use
-the specified version of Python rather than the version detected by
-\fBpython_version\fR.
-.TP
-.B python_mod_cleanup \fI< dir1 > < dir2 >\fR
-Recursively searches specified directories (or /usr/lib/python*/site-packages
-if called with no arguments) removing orphaned bytecode (.pyc/.pyo files with
-no corresponding .py file).
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/python.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/python.eclass.5,v 1.1.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "RPM.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-rpm.eclass \- convienence class for extracting RPM's
-.SH "DESCRIPTION"
-The \fBrpm\fR eclass exists in order to unpack RPM's for you. This
-way developers dont have to keep employing their own tricks just to
-extract the source archives from an RPM. The eclass will define the
-\fBsrc_unpack\fR function and do all the unpacking for you. The
-unpack function will utilize either \fBrpmoffset\fR or \fBrpm2cpio\fR to
-unpack the RPM. If both exist on the system, then \fBrpm2cpio\fR
-will be utilized.
-.SH "VARIABLES"
-.TP
-.B USE_RPMOFFSET_ONLY = \fI"[0|1]"\fR
-If you want to force the RPM extractor to utilize \fBrpmoffset\fR
-even if \fBrpm2cpio\fR is detected, then just set this variable to 1.
-.SH "FUNCTIONS"
-.TP
-.B rpm_unpack \fI"<file to unpack>"\fR
-Unpack an RPM file in the same manner that \fBunpack\fR unpacks any
-other archive. The contents of the RPM will be extracted to \fB${WORKDIR}\fR.
-.TP
-.B rpm_src_unpack
-This replacement for \fBsrc_unpack\fR will go through \fB${A}\fR and
-unpack all the files. If the file is an RPM, then \fBrpm_unpack\fR
-will be called. Otherwise the default \fBunpack\fR function will be
-utilized.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/rpm.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/rpm.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH RUBY.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-ruby.eclass \- functions to ease installation of Ruby software
-.SH DESCRIPTION
-The \fBruby\fR eclass provides an interface designed to ease the installation
-and integration of Ruby software.
-.SH VARIABLES
-.TP
-.B RUBY = \fI"/usr/bin/ruby"\fR
-Defines the location of the Ruby binary. Defaults to '/usr/bin/ruby'.
-.TP
-.B USE_RUBY = \fI"ruby18"\fR
-Defines a white-space delimited list of supported Ruby versions. This variable
-can be set to "any" if the ebuild only installs version independant files.
-Possible values for this variable include \fBany\fR, \fBruby16\fR, \fBruby18\fR,
-and \fBruby19\fR.
-.TP
-.B RUBY_ECONF = \fI"--with-foo"\fR
-Defines any extra arguments to pass to econf.
-.TP
-.B PATCHES = \fI"foo.patch *.diff"\fR
-Defines a white-space delimited list of patches that should be applied. In
-addition to literal filenames, globbing may also be used.
-.SH FUNCTIONS
-.TP
-.B ruby_einstall
-Default einstall that executes standard Ruby installation scripts in addition
-to installing all .rb files into the local Ruby site directory.
-.TP
-.B erubydoc
-Installs documentation, HTML, and examples into /usr/share/doc/\fB${PF}\fR.
-.TP
-.B ruby_src_compile
-Default src_compile that simply executes \fBruby_econf\fR and \fBruby_emake\fR.
-.TP
-.B ruby_src_install
-Default src_install that simply runs \fBruby_einstall\fR and \fBerubydoc\fR.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/ruby.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/ruby.eclass.5,v 1.1.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "SSL-CERT.ECLASS" "5" "Oct 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-ssl-cert.eclass \- provides common SSL certificates installation routines
-.SH "DESCRIPTION"
-The \fBssl-cert\fR eclass contains a function used to generate and
-install SSL certificates and related files for testing and initial
-configuration purposes of TLS/SSL compatible services.
-.SH "VARIABLES"
-.TP
-\fBSSL_DAYS =\fR \fI"730"\fR (2 years)
-The generated certificate will be expired after this many days.
-.TP
-\fBSSL_BITS =\fR \fI"1024"\fR
-The number of bits used for the certificate keys.
-.TP
-\fBSSL_COUNTRY =\fR \fI"US"\fR
-The country (code only) for the generated certificate.
-.TP
-\fBSSL_STATE =\fR \fI"California"\fR
-The state (no abbreviation) for the generated certificate.
-.TP
-\fBSSL_LOCALITY =\fR \fI"Santa Barbara"\fR
-The locality (city) name for the generated certificate.
-.TP
-\fBSSL_ORGANIZATION =\fR \fI"SSL Server"\fR
-The organization (business) name for the generated certificate.
-.TP
-\fBSSL_UNIT =\fR \fI"For Testing Purposes Only"\fR
-The organizational unit (department) name for the generated certificate.
-.TP
-\fBSSL_COMMONNAME =\fR \fI"localhost"\fR
-The hostname (FQDN) for the generated certificate.
-.TP
-\fBSSL_EMAIL =\fR \fI"root@localhost"\fR
-The technical contact (email address) for the generated certificate.
-.SH "FUNCTIONS"
-.TP
-.B docert \fI<cert1>\fR \fI[cert2 ...]\fR
-This function will generate and install the requested certificates into
-the current \fB${INSDESTTREE}\fR location. For example:
-.br
-\fBinsinto\fR \fI/etc/ssl/server\fR
-.br
-\fBdocert\fR \fImail\fR \fIimap\fR || die "Error creating certificates"
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/ssl-cert.eclass
-.SH "AUTHORS"
-Max Kalika <max@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/ssl-cert.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "STARDICT.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-startdict.eclass \- convienence class to do stardict dictionary installations
-.SH "DESCRIPTION"
-The \fBstartdict\fR eclass contains appropriate variables and functions
-to quickly make ebuild's for stardictionaries. The eclass will define
-\fBsrc_compile\fR and \fBsrc_install\fR functions for you. All you
-need to do is to set the \fBDICT_SUFFIX\fR, \fBDICT_P\fR, \fBFROM_LANG\fR,
-and \fBTO_LANG\fR variables before inheriting the eclass.
-.SH "VARIABLES"
-.TP
-.B FROM_LANG = \fI"From this language"\fR
-What language is the dictionary translating from? If you have an
-English to German dictionary, this variable would be set to 'English'.
-.TP
-.B TO_LANG = \fI"To this language"\fR
-What language is the dictionary translating to? If you have an
-English to German dictionary, this variable would be set to 'German'.
-.TP
-.B DICT_PREFIX = \fI"SRC_URI prefix, like 'dictd_www.mova.org_'"\fR
-SRC_URI prefix, like "dictd_www.mova.org_".
-.TP
-.B DICT_SUFFIX = \fI"SRC_URI after the prefix"\fR
-SRC_URI after the prefix.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/stardict.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/stardict.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH SUBVERSION.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-subversion.eclass \- provides subversion fetching functions
-.SH DESCRIPTION
-The \fBsubversion\fR eclass provides functions that enable the ebuild author
-to create 'live' ebuilds that fetch the program's sources from a subversion
-repository.
-.br
-
-\fBNOTE\fR: At the very minimum, the \fBsubversion\fR eclass requires the
-\fBESVN_REPO_URI\fR variable to be set (see below).
-.SH VARIABLES
-.TP
-.B "ESVN_REPO_URI" = \fI"svn://foo/bar/trunk"\fR
-This variable sets the URI from which the sources will be fetched. The
-\fBsubversion\fR eclass supports fetching from the following protocols:
-\fIhttp\fR, \fIhttps\fR, and \fIsvn\fR. This variable is required to be set.
-.TP
-.B "ESVN_STORE_DIR" = \fI"${DISTDIR}/svn-src"\fB
-This variable defines the location in which the fetched sources will be kept.
-The default value is '${DISTDIR}/svn-src' and should be sufficient in most
-cases.
-.TP
-.B "ESVN_FETCH_CMD" = \fI"svn checkout"\fB
-This variable defines the command used for initial checkout and defaults to 'svn checkout'.
-.TP
-.B "ESVN_UPDATE_CMD" = \fI"svn update"\fB
-This variable defines the command used for updating sources and defaults to 'svn update'.
-.TP
-.B "ESVN_PROJECT" = \fI"foobar"\fB
-This variable defines the name of the project and defaults to '${PN/-svn}'.
-.TP
-.B "ESVN_BOOTSTRAP" = \fI"autogen.sh"\fB
-This variable defines the name of the bootstrap script to execute in
-preparation for the build process. This variable is empty by default. Note:
-"./" is automatically prepended, so it is unnecessary for the ebuild author to
-do so.
-.TP
-.B "ESVN_PATCHES" = \fI"foo.patch *.diff"\fB
-This variable defines a list of patches to apply prior to fetching the sources.
-In addition to literal filenames, you may also use globbing such as *.diff.
-This variable is empty by default.
-.SH FUNCTIONS
-.TP
-.B subversion_src_unpack
-The default \fBsrc_unpack\fR provided by the \fBsubversion\fR eclass simply
-fetches the program's sources from the URI specified by \fBESVN_REPO_URI\fR,
-applies any patches specified by \fBESVN_PATCHES\fR, and then executes the
-bootstrap script specified by \fBESVN_BOOTSTRAP\fR.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/subversion.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/subversion.eclass.5,v 1.1.2.3 2005/05/10 11:30:32 swegener Exp $
+++ /dev/null
-.TH TLA.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-tla.eclass \- provides generic tla fetching functions
-.SH DESCRIPTION
-The \fBtla\fR eclass provides an interface to easily allow ebuild authors to
-create 'live' tla ebuilds that fetch their sources from a tla repository.
-.SH VARIABLES
-.TP
-.B ETLA_TLA_CMD = \fI"tla"\fR
-Defines tla executable. Defaults to 'tla'.
-.TP
-.B ETLA_GET_CMD = \fI"get"\fR
-Defines tla get option. Defaults to 'get'.
-.TP
-.B ETLA_UPDATE_CMD = \fI"replay"\fR
-Defines tla update option. Defaults to 'replay'.
-.TP
-.B ETLA_TOP_DIR = \fI"${DISTDIR}/tla-src"\fR
-Defines location where fetched sources will be kept. Defaults to '${DISTDIR}/tla-src'.
-.TP
-.B ETLA_VERSION = \fI"foo@bar.com--archive-name/category--branch--version"\fR
-Defines tla version in the above format. This variable will be passed as the
-argument to a tla subcommand such as get, replay, etc.
-.TP
-.B ETLA_CACHE_DIR = \fI"${ELTA_VERSION}"\fR
-Defines the location where the version shall be cached. This location is
-relative to \fBETLA_TOP_DIR\fR. Defaults to '\fBETLA_VERSION\fR'.
-.TP
-.B ETLA_ARCHIVES
-Defines a whitespace-delimited list of significant archive URI's. This variable
-should at least include the URI of the archive that the wanted version is stored
-in.
-.TP
-.B ETLA_CLEAN
-Defines whether or not to fetch a clean copy of sources if there is already a
-working copy available. If set, the working copy will be removed and a fresh
-copy will be fetched. Otherwise, the working copy will just be updated (via
-\fBETLA_UPDATE_CMD\fR). This variable is unset by default.
-.SH FUNCTIONS
-.TP
-.B tla_src_unpack
-Default src_unpack that fetches the sources and places them in \fB${WORKDIR}\fR/\fB${P}\fR.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/tla.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/tla.eclass.5,v 1.1.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "TOOLCHAIN-FUNCS.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-toolchain-funcs.eclass \- functions to get commonly needed info about the
-toolchain (binutils/gcc/glibc/etc...)
-.SH "DESCRIPTION"
-The \fBtoolchain-funcs\fR eclass contains a suite of functions that are
-used to glean information about the toolchain that is used to compile.
-This allows developers to worry about gcc specs rather than figuring
-out how to find the specs in the first place.
-.SH "TOOL FUNCTIONS"
-.TP
-.B tc-getAR
-Returns the name of the binutils archiver. Usually 'ar'.
-.TP
-.B tc-getAS
-Returns the name of the assembler. Usually 'as'.
-.TP
-.B tc-getBUILD_CC
-Returns the name of the compiler for the build system.
-Useful only when you have to compile and run a utility while
-building the package.
-.TP
-.B tc-getCC
-Returns the name of the C compiler binary. Usually 'gcc'.
-.TP
-.B tc-getCXX
-Returns the name of the C++ compiler binary. Usually 'g++'.
-.TP
-.B tc-getF77
-Returns the name of the fortran compiler.
-.TP
-.B tc-getGCJ
-Returns the name of the java compiler. Usually 'gcj'.
-.TP
-.B tc-getLD
-Returns the name of the linker. Usually 'ld'.
-.TP
-.B tc-getNM
-Returns the name of the symbol/object thingy. Usually 'nm'.
-.TP
-.B tc-getRANLIB
-Returns the name of the archiver indexer. Usually 'ranlib'.
-.SH "MISC FUNCTIONS"
-.TP
-\fBtc-arch\fR [\fITARGET\fR]
-Echo the portage $ARCH that the current toolchain represents.
-Basically this is a drop-in replacment for $ARCH usage. If no
-\fITARGET\fR is specified, then CHOST will be used.
-.TP
-\fBtc-arch-kernel\fR [\fITARGET\fR]
-Echo the kernel $ARCH that the current toolchain represents. If no
-\fITARGET\fR is specified, then CHOST will be used.
-.TP
-\fBtc-endian\fR [\fITARGET\fR]
-Echo 'little' or 'big' based upon what the current toolchain represents.
-If no \fITARGET\fR is specified, then CHOST will be used.
-.TP
-\fBtc-export\fR <\fBlist of variables\fR>
-Quickly export \fBlist of variables\fR to the environment. Much easier
-than exporting each idividual variable at a time.
-
-For example: \fBtc-export\fR CC CXX AR RANLIB
-.TP
-.B tc-is-cross-compiler
-Return shell true/false based upon whether the current building
-setup is for a cross compiler.
-.SH "VERSION FUNCTIONS"
-.TP
-.B gcc-fullversion
-Returns the version as by `$CC -dumpversion`.
-.br
-GCC \fI2.95.3\fR will return \fI2.95.3\fR
-.br
-GCC \fI3.2.1\fR will return \fI3.2.1\fR
-.TP
-.B gcc-version
-Returns the version, but only the <major>.<minor>.
-.br
-GCC \fI2.95\fR.3 will return \fI2.95\fR
-.br
-GCC \fI3.2\fR.1 will return \fI3.2\fR
-.TP
-.B gcc-major-version
-Returns the Major version.
-.br
-GCC \fI2\fR.95.3 will return \fI2\fR
-.br
-GCC \fI3\fR.2.1 will return \fI3\fR
-.TP
-.B gcc-minor-version
-Returns the Minor version.
-.br
-GCC 2.\fI95\fR.3 will return \fI95\fR
-.br
-GCC 3.\fI2\fR.1 will return \fI2\fR
-.TP
-.B gcc-micro-version
-Returns the Micro version.
-.br
-GCC 2.95.\fI3\fR will return \fI3\fR
-.br
-GCC 3.2.\fI1\fR will return \fI1\fR
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.SH "FILES"
-.BR /usr/portage/eclass/toolchain-funcs.eclass
-.SH "AUTHORS"
-Mike Frysinger <vapier@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/toolchain-funcs.eclass.5,v 1.1.2.2 2005/01/15 00:19:23 vapier Exp $
+++ /dev/null
-.TH VERSIONATOR.ECLASS 5 "Nov 2004" "Portage 2.0.51" portage
-.SH NAME
-versionator.eclass \- provides functions for easy manipulation of versions
-.SH DESCRIPTION
-The \fBversionator\fR eclass provides functions to ease manipulation of
-software versions. The most common use of this eclass is for manipulation of
-the \fB${PV}\fR variable (and saving the result in a variable such as
-\fB${MY_PV}\fR).
-.SH FUNCTIONS
-\fBNOTE\fR: the following functions all operate on a version string (denoted
-as \fIPV\fR in this manual page), which defaults to \fB${PV}\fR if omitted.
-See the eclass for example version strings and their respective results.
-.TP
-.B get_all_version_components \fI< PV >\fR
-Splits PV into its component parts.
-.TP
-.B get_version_components \fI< PV >\fR
-Splits PV into its component parts, ignoring '.', '-', and '_'.
-.TP
-.B get_major_version \fI< PV >\fR
-Retrieves major version from PV.
-.TP
-.B get_version_component_range \fI[ RANGE ] < PV >\fR
-Retrieves a component or range of components, RANGE, from PV. RANGE may be
-a single number for a particular component, a range such as 1-2 for a range
-of components, or a range such as 2- for that component and everything after it.
-.TP
-.B get_after_major_version \fI< PV >\fR
-Retrieves everything after the major version and its separator (if present).
-.TP
-.B replace_version_separator \fI[ N ] [ SEP ] < PV >\fR
-Replaces the Nth separator of PV with separator, SEP. If N is a character
-literal (eg. '-'), the first separator of this kind is replaced.
-.TP
-.B replace_all_version_separators \fI[ SEP ] < PV >\fR
-Replaces all version separators in PV with separator, SEP.
-.TP
-.B delete_version_separator \fI[ N ] < PV >\fR
-Deletes the Nth separator of PV. If N is a character literal (eg. '-'), the first
-separator of this kind is deleted.
-.TP
-.B delete_all_version_separators \fI<PV>\fR
-Deletes all version separators in PV.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.BR /usr/portage/eclass/versionator.eclass
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/versionator.eclass.5,v 1.1.2.4 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH VIM-PLUGIN.ECLASS 5 "Dec 2004" "Portage 2.0.51" portage
-.SH NAME
-vim-plugin.eclass \- functions to ease installation of Vim plugins
-.SH DESCRIPTION
-The \fBvim-plugin\fR eclass provides functions meant to simplify the
-installation of Vim plugins into a version-independent directory,
-/usr/share/vim/vimfiles.
-.SH VARIABLES
-.TP
-.B VIM_PLUGIN_HELPFILES
-Defines a white-space delimited list of help files, used soley for informing
-the user how to access them within Vim.
-.TP
-.B VIM_PLUGIN_HELPTEXT
-Defines help text to display. Used only if \fBVIM_PLUGIN_HELPFILES\fR is unset.
-.TP
-.B VIM_PLUGIN_HELPURI
-Defines a URI where on-line plugin documentation is available. This variable
-is only used if \fBVIM_PLUGIN_HELPFILES\fR and \fBVIM_PLUGIN_HELPTEXT\fR are
-unset.
-.TP
-.B VIM_PLUGIN_MESSAGES
-Defines a white-space delimited list of settings that the Vim plugin makes use
-of. Currently, only 'filetype' is supported; any other specified settings will
-be ignored.
-.SH FUNCTIONS
-.TP
-.B update_vim_afterscripts
-Creates scripts in /usr/share/vim/vimfiles/after that are comprised of the
-snippets located in /usr/share/vim/vimfiles/after/*/*.vim.d. In addition,
-any stale scripts that were previously generated by this function are removed.
-.TP
-.B display_vim_plugin_help
-Displays a message containing plugin help information. This function checks
-the variables \fBVIM_PLUGIN_HELPFILES\fR, \fBVIM_PLUGIN_HELPTEXT\fR, and
-\fBVIM_PLUGIN_HELPURI\fR (in that order) and displays the first one that is
-defined. In addition, any setting-specific messages that correspond to
-settings listed in \fBVIM_PLUGIN_MESSAGES\fR will be displayed.
-.TP
-.B vim-plugin_src_install
-Default src_install. Installs plugin documentation prior to installing the
-entire contents of \fB${S}\fR to /usr/share/vim/vimfiles.
-.TP
-.B vim-plugin_pkg_postinst
-Default pkg_postinst that updates Vim helptags (see \fBupdate_vim_helptags\fR
-in vim-doc.eclass), updates after scripts, and calls \fBdisplay_vim_plugin_help\fR.
-.TP
-.B vim-plugin_pkg_postrm
-Default pkg_postrm that updates Vim helptags (see \fBupdate_vim_helptags\fR
-in vim-doc.eclass), updates after scripts, and removes any empty directories
-in /usr/share/vim/vimfiles.
-.SH PACKAGING
-In general, tarballs for plugins cannot be used directly because of vim.org's
-idiosyncratic download system. Instead, a Gentoo-specific tarball must be made
-with the following format for contents:
-
-.nf
- packagename-version/
- packagename-version/doc/
- packagename-version/doc/whatever.txt
- packagename-version/plugin/
- packagename-version/plugin/whatever.vim
- packagename-version/syntax/
- packagename-version/syntax/whatever.vim
-.fi
-.SH PACKAGE NAMING CONVENTIONS
-Where possible, the upstream script name should be used as the package name.
-For packages which provide syntax or filetype files, the name should be suffixed
-with "-syntax" (for example, "app-vim/gentoo-syntax", "app-vim/fluxbox-syntax",
-"app-vim/selinux-syntax").
-.SH PACKAGE VARIABLE CONVENTIONS
-The canonical form for the HOMEPAGE variable for vim.org scripts is
-http://www.vim.org/scripts/script.php?script_id=123.
-.SH REPORTING BUGS
-Please report bugs via http://bugs.gentoo.org/
-.SH SEE ALSO
-.BR ebuild (5)
-.SH FILES
-.nf
-.B /usr/portage/eclass/vim-plugin.eclass
-.B /usr/portage/eclass/vim-doc.eclass
-.fi
-.SH AUTHORS
-Aaron Walker <ka0ttic@gentoo.org>
-.SH CVS HEADER
-$Id: /var/cvsroot/gentoo-src/portage/man/vim-plugin.eclass.5,v 1.1.2.2 2005/01/15 00:19:36 vapier Exp $
+++ /dev/null
-.TH "VIM.ECLASS" "5" "Jun 2003" "Portage 2.0.51" "portage"
-.SH "NAME"
-vim.eclass \- common build routines for vim-core, vim and gvim
-.SH "DESCRIPTION"
-The \fBvim\fR eclass contains a suite of functions that are used to
-build \fBvim-core\fR, \fBvim\fR and \fBgvim\fR. The vim-core ebuild
-contains the common files installed in /usr/share/vim, /usr/share/doc
-and /etc/vim, as well as the binaries xxd and vimtutor. The vim
-ebuild contains the terminal-based version of vim. The gvim ebuild
-contains the graphical version of vim. All three of these are built
-from common source, common patches and using mostly-common configure
-options.
-.P
-There are no functions to define in an ebuild using \fBvim.eclass\fR
-because the eclass does all the unpacking, compilation and
-installation.
-.SH "VARIABLES"
-.TP
-.B VIM_VERSION = \fI"version string"\fR
-This variable is important because the ebuild version (for example
-6.2_pre5) corresponds to a vim version (for example 6.2e) but there is
-no way to make that jump without help from the ebuild author.
-Historically there was a method in the vim.eclass to calculate the vim
-version from the ebuild version, but that meant that the ebuild author
-had to make sure the ebuild was correctly versioned each time. To
-avoid that headache, it became easier to simply specify
-\fBVIM_VERSION\fR in the ebuild itself.
-.TP
-.B VIM_GENTOO_PATCHES = \fI"filename"\fR
-The filename of the Gentoo patches to apply. It's not always
-necessary to update the Gentoo patches for a new version of vim,
-so this variable separates the ebuild and vim versions from the patch
-tarball version. Take a look at
-\fBvim-6.2.011-gentoo-patches.tar.bz2\fR
-for an example of the patch directory layout.
-.TP
-.B VIM_ORG_PATCHES = \fI"filename"\fR
-The filename of the vim patches to apply. This is a tarball of
-patches from \fBftp://ftp.vim.org/pub/vim/patches/\fR which apply to
-the current version. See \fBvim-6.2.011-patches.tar.bz2\fR for an
-example of the vim.org patch tarballs.
-.SH "REPORTING BUGS"
-Please report bugs via http://bugs.gentoo.org/
-.SH "SEE ALSO"
-.BR ebuild (5)
-.BR vim (1)
-.SH "FILES"
-.BR /usr/portage/eclass/vim.eclass
-.SH "AUTHORS"
-Aron Griffis <agriffis@gentoo.org>
-.br
-Ryan Phillips <rphillips@gentoo.org>
-.br
-Seemant Kulleen <seemant@gentoo.org>
-.SH "CVS HEADER"
-$Id: /var/cvsroot/gentoo-src/portage/man/vim.eclass.5,v 1.3.2.1 2005/01/15 00:19:36 vapier Exp $
projects / portage.git / commitdiff