Rpm packaging on Suse Linux Post: 302496438

Sponsored Content

Operating Systems Linux SuSE Rpm packaging on Suse Linux Post 302496438 by dirshah on Monday 14th of February 2011 05:11:48 AM

02-14-2011

Registered User

Rpm packaging on Suse Linux

Hi All,
I am new to linux. Still I am asked to package a war file as an RPM package. That is an unusual RPM packaging(To me). If you guys could guide me, on how to do that, will be great. I have a war file inside a folder, that folder is inside a tar file as a SOURCE for RPM package. The structure is like below.

--RPMS
--SOURCES
--tasmportlets-1.tar.gz(its a tar file)
--tasmportlets-1(its a folder)
--tasmportlets.war
--BUILD
--SPECS
--mySpecs.spec
--SRPMS

I simply want that the war file from sources is transferred to the web app of my tomcat server through RPM. I try to package it as an RPM, but its always giving me errors in %build stage. When I try to remove %build from stage from the spec file, then it says command missing.

Can anyone please help me here Or point me in the right direction? An example will be great.

My system details are:
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 1
LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64"

Thanks in advance.

dirshah

View Public Profile for dirshah

Find all posts by dirshah

4 More Discussions You Might Find Interesting

1. 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...

2. Shell Programming and Scripting

build rpm with SPEC file for packaging .jar and some .sh files..

Good day people, Hereby wish to have your advise for below: I have some .jar files, some script files (install.sh, action.sh) , and a libaes.so file. Basically, the .jar files compute the operation of my system and define the working directory for my system. My current scenario: i trigger...

3. Linux

rpm packaging issue for unixodbc driver manager

Hi All, I am trying to make rpm package for unixODBC driver manager 2.3.0 using below spec file. During rpmbuild i am getting the error. Can you pls advice how we can overcome this issue %define name unixODBC %define ver 2.3.0 %define prefix /usr %define sysconfdir /etc %define libdir...

4. Red Hat

RPM packaging a directory of files

Hi, I wonder if anyone can point me in the right direction I have a requirement to distribute a set of admin scripts that currently sit in an SVN repo by packaging them up in an RPM so that they can me unpacked to the correct location by simply installing the package .. e.g. 'yum install...

LEARN ABOUT CENTOS

scap-as-rpm

scap-as-rpm(8)						  System Administration Utilities					    scap-as-rpm(8)

NAME

       scap-as-rpm - manual page for scap-as-rpm

DESCRIPTION

       usage: scap-as-rpm [-h] [--pkg-name PKG_NAME] [--pkg-version PKG_VERSION]

	      [--pkg-release   PKG_RELEASE]   [--pkg-summary  PKG_SUMMARY]  [--pkg-license  PKG_LICENSE]  [--pkg-scap-location	PKG_SCAP_LOCATION]
	      [--rpm-destination RPM_DESTINATION] [--srpm-destination SRPM_DESTINATION] FILE [FILE ...]

       Takes given SCAP input(s) and makes an RPM package that contains them. The result  RPM  can  be	installed  using  #  yum  install  ./pack-
       age-name-1-1.rpm which will put the contents into /usr/share/xml/scap. No dependency on openscap or scapworkbench is enforced in the output
       package so you can use any SCAP-capable scanner to evaluate the content.

   positional arguments:
       FILE   List of files that should be put into the result package. These should be SCAP XML files but such requirement is not enforced.

   optional arguments:
       -h, --help
	      show this help message and exit

       --pkg-name PKG_NAME
	      Name of the RPM package, if none is provided the basename of the first SCAP input is used. Ex.: xyzsecurity-guide

       --pkg-version PKG_VERSION

       --pkg-release PKG_RELEASE

       --pkg-summary PKG_SUMMARY
	      Optional short description of the package.

       --pkg-license PKG_LICENSE
	      Short name of the license that you want to publish the package under. Ex.: GPLv2+, BSD, ...

       --pkg-scap-location PKG_SCAP_LOCATION
	      Folder where SCAP files are supposed to be installed.  Each package will have its own folder inside this folder. RPM  variables  can
	      be used and will be expanded as usual. It is recommended to keep the default settings.

       --rpm-destination RPM_DESTINATION
	      The folder (absolute or relative to CWD) where the result RPM shall be saved.

       --srpm-destination SRPM_DESTINATION
	      The folder (absolute or relative to CWD) where the result SRPM shall be saved.

scap-as-rpm							   November 2013						    scap-as-rpm(8)