epm man page on DragonFly

Man page or keyword search:  
man Server   44335 pages
apropos Keyword Search (all sections)
Output format
DragonFly logo
[printable version]

epm(1)				Michael R Sweet				epm(1)

NAME
       epm - create software packages.

SYNOPSIS
       epm  [  -a  architecture	 ]  [  -f format ] [ -g ] [ -k ] [ -m name ] [
       -n[mrs] ] [ -s setup.ext ] [ --depend ] [ --help ] [ --keep-files  ]  [
       --output-dir  directory ] [ --setup-image setup.ext ] [ --setup-program
       /foo/bar/setup ] [ --setup-types setup.types ]  [  -v  ]	 [  name=value
       name=value ] product [ listfile ]

DESCRIPTION
       epm(1) generates software packages complete with installation, removal,
       and (if necessary) patch	 scripts.   Unless  otherwise  specified,  the
       files required for product are read from a file named "product.list".

OPTIONS
       The following options are recognized:

       -a architecture
	    Specifies  the actual architecture for the software.  Without this
	    option  the	 generic  processor  architecture  is  used  ("intel",
	    "sparc", "mips", etc.)

       -f aix
	    Generate  an  AIX distribution suitable for installation on an AIX
	    system.

       -f bsd
	    Generate a BSD distribution suitable for installation on  a	 Free‐
	    BSD, NetBSD, or OpenBSD system.

       -f deb
	    Generate  a	 Debian	 distribution  suitable	 for installation on a
	    Debian Linux system.

       -f inst

       -f tardist
	    Generate an IRIX distribution suitable for installation on an sys‐
	    tem running IRIX.

       -f lsb

       -f lsb-signed
	    Generate  RPM packages for LSB-conforming systems.	The lsb-signed
	    format uses the GPG private key you have defined  in  the  ~/.rpm‐
	    macros file.

       -f native
	    Generate a native distribution.  This uses rpm for Linux, inst for
	    IRIX, pkg for Solaris, swinstall for HP-UX, bsd for FreeBSD,  Net‐
	    BSD,  and  OpenBSD, and osx for OS X.  All other operating systems
	    default to the portable format.

       -f osx

       -f osx-signed
	    Generate an OS X software package.	The osx-signed format uses the
	    signing identity in the EPM_SIGNING_IDENTITY environment variable.

       -f pkg
	    Generate an AT&T software package.	These are used primarily under
	    Solaris.

       -f portable
	    Generate a portable distribution based on shell  scripts  and  tar
	    files.   The  resulting  distribution is installed and removed the
	    same way on all operating systems. [default]

       -f rpm

       -f rpm-signed
	    Generate a Red Hat Package Manager ("RPM")	distribution  suitable
	    for installation on a Red Hat Linux system.	 The rpm-signed format
	    uses the GPG private key you  have	defined	 in  the  ~/.rpmmacros
	    file.

       -f setld
	    Generate a Tru64 (setld) software distribution.

       -f slackware
	    Generate a Slackware Linux software distribution.

       -f swinstall

       -f depot
	    Generate a HP-UX software distribution.

       -g   Disable stripping of executable files in the distribution.

       -k   Keep  intermediate (spec, etc.) files used to create the distribu‐
	    tion in the distribution directory.

       -m name
	    Specifies the platform name as a string.  The default  is  to  use
	    the auto-generated name from the -n option.

       -n[mrs]
	    Specifies  the  operating  system  and machine information that is
	    included in the package name.  Distributions  normally  are	 named
	    "product-version-system-release-machine.ext" and "product-version-
	    system-release-machine-patch.ext" for  patch  distributions.   The
	    "system-release-machine"  information  can be customized or elimi‐
	    nated using the appropriate trailing letters.  Using -n by	itself
	    will  remove the "system-release-machine" string from the filename
	    entirely.  The letter 'm'  includes	 the  architecture  (machine).
	    The	 letter	 'r'  includes the operating system version (release).
	    The letter 's' includes the operating system name.

       -s setup.ext

       -v   Increases the amount of information that is reported.  Use	multi‐
	    ple v's for more verbose output.

       --depend
	    Lists the dependent (source) files for all files in the package.

       --output-dir directory
	    Specifies  the  directory for output files.	 The default directory
	    is based on the operating system, version, and architecture.

       --setup-image setup.ext
	    Include the ESP Software Wizard with the specified image file with
	    the distribution.  This option is currently only supported by por‐
	    table distributions.

       --setup-program /foo/bar/setup
	    Specifies the setup executable to use with the distribution.  This
	    option is currently only supported by portable distributions.

       --setup-types setup.types

       Specifies  the setup.types file to include with the distribution.  This
       option is currently only supported by portable distributions.

ENVIRONMENT
       The following environment variables are supported by epm

       The common name that should be used when signing a package.

LIST FILES
       The EPM list file format is now described in the epm.list(5) man page.

SEE ALSO
       epminstall(1), mkepmlist(1), epm.list(5), setup(1).

COPYRIGHT
       Copyright © 1999-2015 by Michael R Sweet, All Rights Reserved.

       This program is free software; you can redistribute it and/or modify it
       under  the  terms of the GNU General Public License as published by the
       Free Software Foundation; either version 2, or  (at  your  option)  any
       later version.

       This  program  is  distributed  in the hope that it will be useful, but
       WITHOUT ANY  WARRANTY;  without	even  the  implied  warranty  of  MER‐
       CHANTABILITY  or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General
       Public License for more details.

1 September 2015	      ESP Package Manager			epm(1)
[top]

List of man pages available for DragonFly

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net