Closed
Bug 766424
Opened 13 years ago
Closed 13 years ago
rss: work out the desired fpm packaging options for nfast
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Atoll, Assigned: Atoll)
Details
(Whiteboard: [qa-])
today, it's -n packagename and the supplement package gets -d dependson. review actual fpm option set and make sure we're doing good things, and then put the fpm command into VCS somewhere along with the resulting spec and a link to the tarball.
currently i have grabbed the iso from http://www.fs2.com/IT/Thales/nCSS-linux64-user-11.50.iso
mounted it, extracted the /linux/ directory, went into the nfast sub directory and ran the following script. Note that it's missing packaging of the kernel modules, see bug 766442 for that. The versions are taken from "versions.txt" in the same nfast subdir.
#!/bin/sh
#Increment SUBREL when you repackage
SUBREL=2
PREFIX='nfast-'
function mkpkg()
{
name=$PREFIX$1
version=$2
file=$3
shift;shift;shift;
rest=$*
fpm --iteration $SUBREL -n $name -s tar -t rpm \
--description "Packaged needed for nCSS/nFast/nCipher/Thales HSM" -v $version \
-p $name-$version-$SUBREL.rpm $rest $file
}
mkpkg hwcrhk 1.14.6cam269 hwcrhk/user.tar --depends ${PREFIX}hwsp
mkpkg hwsp 2.22.58cam35 hwsp/agg.tar
mkpkg ctls 2.22.58cam131 ctls/agg.tar --depends ${PREFIX}hwsp
Updated•13 years ago
|
Whiteboard: [qa-]
infrasec managing this rpm
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•