Sponsored Content
Full Discussion: Custom Packaging scripts
Operating Systems AIX Custom Packaging scripts Post 302311509 by vibhor_agarwali on Wednesday 29th of April 2009 12:52:41 AM
Old 04-29-2009
Can you please name those hooks:

I tried giving "pre-remove", it said:
0503-878 mkinstallp: Unknown keyword (Pre-remove) in Test.tmplt

where Test.tmplt is my template file
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sun Solaris Packaging

Hi Could somebody explain what Sun Packaging is What are its uses How to package and things like that I would appreciate if u could give me some study materials or a url where I could get more details on that Thanks in advance Ram (1 Reply)
Discussion started by: ramukmar
1 Replies

2. HP-UX

Output of Custom package scripts to terminal

Hi, I am doing some testing with creation of depots on HP-UX systems (11.11). Want to display some echo statements based on the processing during checkinstall, pre & postinstall scripts on the terminal. The echo statements are getting directed to /var/adm/sw/swagent.log I want to display... (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies

3. Red Hat

RPM Packaging doubt!

Hi, I need to create an RPM package for my java application. Already build package for that application avail;able. I need to create binary RPM package for my java application. For that in spec file, do I need to write any script kind of thing to install my package. any one have idea... (1 Reply)
Discussion started by: ram.sj
1 Replies

4. Shell Programming and Scripting

sh packaging

I wrote a sh program with many options and lot of cool stuff and I will to learn how to package it. So ppl could downlaod it and use it just like ls cp .. So if I have BUX.sh ppl could type BUX -r-r on the command line and it just work or I could have BUM man Also I like to offer them... (4 Replies)
Discussion started by: just_linux
4 Replies

5. UNIX for Dummies Questions & Answers

Help with packaging tools.

Hai friends, I have used the dpkg command to install the package. This package is created my me. This has only one "C" file. I checked my module status by "lintian" command as a root. When I execute the command it gives me following messages... (0 Replies)
Discussion started by: Nila
0 Replies

6. Homework & Coursework Questions

: Packaging in Python

Dear All, I python program which print "Hello World". I want to run this program in 100 system. I dont want to copy and run this script. I want to make .deb package which is easy to install by gui double click itself. Is this possible ?, If yes, how to do. PS: I am not using glade... (1 Reply)
Discussion started by: kiranpulsar2007
1 Replies

7. Solaris

Packaging driver for NIC

Hi guys My friend needs nfo driver for his Solaris box. I installed that driver for myself from scratch and he needs that driver in SVR4 format. I downloaded source code and run make and this is the point I don't how to proceed. How can I recognize which needs go to the package ? Does make... (0 Replies)
Discussion started by: solaris_user
0 Replies

8. Shell Programming and Scripting

Packaging database with script

So this is kind of an odd question. Our school uses a very complicated management suite for student schedules. I wanted a way to look up a students schedule from a CSV without having to load it up in numbers/excel. I wrote a script to do that, but I want to be able to distribute this without... (0 Replies)
Discussion started by: nextyoyoma
0 Replies

9. UNIX for Advanced & Expert Users

A little question: packaging for hpux

Simple question: how to package from source in hpux? On Linux slackware i Use configure,make,make install DESTDIR=$pkg,etc.. and then makepkg -l y -c n. Is possible something similar on hpux? I want to create a depot for samba because,the official doesn't had the winbind pam,and the package on... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies

10. Solaris

Creating IPS packaging

I have installed WL on Solaris 11 and have to create IPS packaging for following directories so that /local/apps/wl/wls12.x /local/apps/wl/oraInventory /local/apps/wl/jdk/jdk1.x Can someone provide the steps for creating IPS or point to the website where I can get help. Thanks,... (2 Replies)
Discussion started by: sam101
2 Replies
epm.list(5)						      Easy Software Products						       epm.list(5)

NAME
epm.list - epm list file format. DESCRIPTION
Each EPM product has an associated list file that describes the files to include with the product. Comment lines begin with the "#" charac- ter and are ignored. All other non-blank lines must begin with a letter, dollar sign ("$"), or the percent sign ("%") as follows: $name=value Sets the named variable to value. Note: Variables set in the list file are overridden by variables specified on the command-line or in the current environment. %arch all Uses following files and directives on all processor architectures. %arch architecture [... architecture] Uses following files and directives on the named processor architectures. %arch !architecture [... architecture] Uses following files and directives on all but the named processor architectures. %copyright copyright notice Sets the copyright notice for the file. %description description text Adds a line of descriptive text to the distribution. Multiple lines are supported. %format format [... format] Uses following files and directives only if the distribution format is the same as format. %format !format [... format] Uses following files and directives only if the distribution format is not the same as format. %if variable [... variable] %if !variable [... variable] %ifdef variable [... variable] %ifdef !variable [... variable] %elseif variable [... variable] %elseif !variable [... variable] %elseifdef variable [... variable] %elseifdef !variable [... variable] %else %endif Conditionally includes lines in the list file. The %if lines include the lines that follow if the named variables are (not) defined with a value. The %ifdef lines include the lines that follow if the named variables are (not) defined with any value. These condi- tional lines cannot be nested. %include filename Includes files listed in filename. %incompat product %incompat filename Indicates that this product is incompatible with the named product or file. %install script or program Specifies a script or program to be run after all files are installed. (This has been obsoleted by the %postinstall directive) %license license file Specifies the file to display as the software license. %literal(section) line %literal(section) <file %literal(section) <<string Specifies format-specific literal data for packaging. Currently only supported for RPM and PKG packages. %packager name of packager Specifies the name of the packager. %patch script or program Specifies a script or program to be run after all files are patched. (This has been obsoleted by the %postpatch directive) %postinstall script or program %postinstall <scriptfile %postinstall <<string Specifies a script or program to be run after all files are installed. %postpatch script or program %postpatch <scriptfile %postpatch <<string Specifies a script or program to be run after all files are patched. %postremove script or program %postremove <scriptfile %postremove <<string Specifies a script or program to be run after removing files. %preinstall script or program %preinstall <scriptfile %preinstall <<string Specifies a script or program to be run before all files are installed. %prepatch script or program %prepatch <scriptfile %prepatch <<string Specifies a script or program to be run before all files are patched. %preremove script or program %preremove <scriptfile %preremove <<string Specifies a script or program to be run before removing files. %product product name Specifies the product name. %readme readme file Specifies a README file to be included in the distribution. %remove script or program Specifies a script or program to be run before removing files. (This has been obsoleted by the %preremove directive) %release number Specifies the release or build number of a product (defaults to 0). %replaces product Indicates that this product replaces the named product. %requires product %requires filename Indicates that this product requires the named product or file. %subpackage %subpackage name Selects the named subpackage; if no name is given, selects the main (parent) package. %vendor vendor or author name Specifies the vendor or author of the product. %version version number Specifies the version number of the product. %system system[-release] [... system[-release]] Specifies that the following files should only be used for the specified operating systems and releases. %system !system[-release] [... system[-release]] Specifies that the following files should not be used for the specified operating systems and releases. %system all Specifies that the following files are applicable to all operating systems. c mode user group destination source C mode user group destination source Specifies a configuration file for installation. The second form specifies that the file has changed or is new and should be included as part of a patch. Configuration files are installed as "destination.N" if the destination already exists. d mode user group destination - D mode user group destination - Specifies a directory should be created when installing the software. The second form specifies that the directory is new and should be included as part of a patch. f mode user group destination source [nostrip()] F mode user group destination source [nostrip()] Specifies a file for installation. The second form specifies that the file has changed or is new and should be included as part of a patch. If the "nostrip()" option is included, the file will not be stripped before the installation is created. f mode user group destination source/pattern [nostrip()] F mode user group destination source/pattern [nostrip()] Specifies one or more files for installation using shell wildcard patterns. The second form specifies that the files have changed or are new and should be included as part of a patch. If the "nostrip()" option is included, the file will not be stripped before the installation is created. i mode user group service-name source ["options"] I mode user group service-name source ["options"] Specifies an initialization script for installation. The second form specifies that the file has changed or is new and should be included as part of a patch. Initialization scripts are stored in /etc/software/init.d and are linked to the appropriate system-spe- cific directories for run levels 0, 2, 3, and 5. Initialization scripts must accept at least the start and stop commands. The optional options following the source filename can be any of the following: order(string) Specifies the relative startup order compared to the required and used system functions. Supported values include First, Early, None, Late, and Last (OSX only). provides(name(s)) Specifies names of system functions that are provided by this startup item (OSX only). requires(name(s)) Specifies names of system functions that are required by this startup item (OSX only). runlevel(levels) Specifies the run levels to use. start(number) Specifies the starting sequence number from 00 to 99. stop(number) Specifies the ending sequence number from 00 to 99. uses(name(s)) Specifies names of system functions that are used by this startup item (OSX only). l mode user group destination source L mode user group destination source Specifies a symbolic link in the installation. The second form specifies that the link has changed or is new and should be included as part of a patch. R mode user group destination Specifies that the file is to be removed upon patching. The user and group fields are ignored. The mode field is only used to deter- mine if a check should be made for a previous version of the file. LIST VARIABLES
EPM maintains a list of variables and their values which can be used to substitute values in the list file. These variables are imported from the current environment and taken from the command-line and list file as provided. Substitutions occur when the variable name is ref- erenced with the dollar sign ($): %postinstall <<EOF echo What is your name: read $$name Your name is $$name EOF f 0555 root sys ${bindir}/foo foo f 0555 root sys $datadir/foo/foo.dat foo.dat Variable names can be surrounded by curley brackets (${name}) or alone ($name); without brackets the name is terminated by the first slash (/), dash (-), or whitespace. The dollar sign can be inserted using $$. SEE ALSO
epm(1) - create software packages epminstall(1) - add a directory, file, or symlink to a list file mkepmlist(1) - make an epm list file from a directory COPYRIGHT
Copyright 1999-2010 by Easy Software Products, 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. 30 December 2010 ESP Package Manager epm.list(5)
All times are GMT -4. The time now is 04:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy