Sponsored Content
Operating Systems Linux Fedora Basic question regarding rpm naming convention. Post 302505545 by pludi on Thursday 17th of March 2011 07:25:51 AM
Old 03-17-2011
The file name isn't fixed to a certain scheme for all distributions. For example, Fedora appends the distribution version it's built for to every RPM. My best guess would be checking the output of rpm -qip <file>
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mandrake rpm question

Env: Mdk 8.1 I downloaded the kernel-source-2.4.8-26mdk.i586.rpm from mandrake. When i try to 'pm -Uv' it, i get an error that i need to install ncurses-devel. The ncurses that is installed with mdk 8.1 is ncurses-5.2-16mdk.i586.rpm and the development version that is avail is... (2 Replies)
Discussion started by: progressdll
2 Replies

2. UNIX Desktop Questions & Answers

Naming convention for Libraries..

Hi All, I need to know standard naming convention for Unix libraries (including all flavours of unix)..As I have gone through some sites and found out The UNIX convention for naming of libraries is lib<name>.so.<major>.<minor>.<revision> so is it statndard . also does it change... (0 Replies)
Discussion started by: rkshukla14
0 Replies

3. Linux

RPM Package question

Hi, I have built one RPM last year. now we have another version of that RPM. in previous release we had few extra files then now. so when user upgrade it those files get deleted by RPM package. We want to retain those files. now for workaround i thought of backing up those file during... (0 Replies)
Discussion started by: ajayyadavmca
0 Replies

4. Shell Programming and Scripting

Naming convention script

OK, so a quick background: I am a sys admin for a 1:1 deployment in academia with Macbooks, totaling around 6,000. Macbooks get shifted around from building to building and go to and from the repair center if hardware repair is needed. Often, some machines will get moved from one building to... (8 Replies)
Discussion started by: tlarkin
8 Replies

5. Shell Programming and Scripting

file naming question

Hi, I need some help! I have a file in which i im splitting into 20 different files each called model_001.in model_002.in etc... i would like to make directory for each file using only the name and not the extension so that the directory names are model_001 model_002 etc. ... (8 Replies)
Discussion started by: olifu02
8 Replies

6. Hardware

Motherboards naming convention

For the selection of motherboards, is there any naming convention in the type numbers? There is usually a brand name and sometimes a version name, but more essential details like form factor, SATA speed and maximum amount of RAM is never given. Is there a reason for that? Is there any background... (2 Replies)
Discussion started by: figaro
2 Replies

7. Shell Programming and Scripting

How to make RPM not write to RPM database if RPM fails to deploy?

How to make RPM not write to RPM database if RPM fails to deploy? IE I create an rpm spec file that contains the following if then exit 1 fi My rpm will fail at deployment, but if I do rpm -qa , I can see the rpm in the rpm db (3 Replies)
Discussion started by: 3junior
3 Replies

8. Shell Programming and Scripting

Concatenate files to one file with naming convention

Hi , i have below files in wrk folder. file names are 1102090001.CLT 1102090003.CLT 1102100019.CLT 1102100020.CLT the above files are concatenate to one file but that concatenate file name must be same naming convention. (date +%y%m%d)and 0001 count. example : concatenate file... (9 Replies)
Discussion started by: krbala1985
9 Replies

9. Red Hat

File System Naming Convention

Hi, I am installing a new RHEL 5 application server containing JBOSS along with other specific 3rd party applications. I know that this usually gets installed in /opt but I was thinking of installing these on a new separtate lv / file system instead. i.e. /<my_new_FS_name> rather than... (6 Replies)
Discussion started by: Duffs22
6 Replies

10. Shell Programming and Scripting

Change the naming convention of the output file

Hi Currently we have nmon running on our Red hat Linux server. The ouput file is now coming with the naming convention as "servername_160321_0010.nmon". The output file naming convention has to be changed as "nmon_servername_daily_2016.03.21_00.00.00" How can we do it ? Any suggestions... (10 Replies)
Discussion started by: newtoaixos
10 Replies
epm(1)							      Easy Software Products							    epm(1)

NAME
epm - create software packages. SYNOPSIS
epm [ -a architecture ] [ -f format ] [ -g ] [ -k ] [ -m name ] [ -n[mrs] ] [ -s setup.xpm ] [ --depend ] [ --help ] [ --keep-files ] [ --output-dir directory ] [ --setup-image setup.xpm ] [ --setup-program /foo/bar/setup ] [ --setup-types setup.types ] [ -v ] [ name=value ... name=value ] product [ listfile ] DESCRIPTION
epm 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". The -a option ("architecture") specifies the actual architecture for the software. Without this option the generic processor architecture is used ("intel", "sparc", "mips", etc.) The -f option ("format") specifies the distribution format: aix Generate an AIX distribution suitable for installation on an AIX system. bsd Generate a BSD distribution suitable for installation on a FreeBSD, NetBSD, or OpenBSD system. deb Generate a Debian distribution suitable for installation on a Debian Linux system. inst, tardist Generate an IRIX distribution suitable for installation on an system running IRIX. lsb, lsb-signed Generate RPM packages for LSB-conforming systems. The lsb-signed format uses the GPG private key you have defined in the ~/.rpmmacros file. native Generate an 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 MacOS X. All other operating systems default to the portable format. osx Generate a MacOS X software package. pkg Generate an AT&T software package. These are used primarily under Solaris. 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] rpm, 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. setld Generate a Tru64 (setld) software distribution. slackware Generate a Slackware Linux software distribution. swinstall, depot Generate a HP-UX software distribution. Executable files in the distribution are normally stripped of debugging information when packaged. To disable this functionality use the -g option. Intermediate (spec, etc.) files used to create the distribution are normally removed after the distribution is created. The -k option keeps these files in the distribution directory. The -s and --setup-image options ("setup") include the ESP Software Wizard with the specified GIF or XPM image file with the distribution. This option is currently only supported by portable and RPM distributions. The --setup-program option specifies the setup executable to use with the distribution. This option is currently only supported by portable distributions. The --setup-types option specifies the setup.types file to include with the distribution. This option is currently only supported by porta- ble distributions. The --output-dir option specifies the directory to place output file into. The default directory is based on the operating system, version, and architecture. The -v option ("verbose") increases the amount of information that is reported. Use multiple v's for more verbose output. The --depend option lists the dependent (source) files for all files in the package. 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 eliminated using the -n option with the appropriate trailing letters. Using -n by itself will remove the "system-release-machine" string from the filename entirely. The "system-release- machine" information can also be customized by using the -m option with an arbitrary string. Debian, IRIX, portable, and Red Hat distributions use the extensions ".deb", ".tardist", "tar.gz", and ".rpm" respectively. LIST FILES
The EPM list file format is now described in the epm.list(5) man page. KNOWN BUGS
EPM does not currently support generation of IRIX software patches. SEE ALSO
epminstall(1) - add a directory, file, or symlink to a list file mkepmlist(1) - make an epm list file from a directory epm.list(5) - epm list file format setup(1) - graphical setup program for the esp package manager COPYRIGHT
Copyright 1999-2008 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. 26 August 2008 ESP Package Manager epm(1)
All times are GMT -4. The time now is 12:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy