All --

I was wondering what's the proper way to include the (pre and post) (install and uninstall) scripts from a .rpm into a SlackBuild script.

I can see how to include the install scriptlets (preinstall and postinstall).

What about the preuninstall and postuninstall scripts ?

See attached get-rpm-scriptlets.txt (added .txt extension to allow attachment) which can extract the scriptlets from a .rpm file.

Save as get-rpm-scriptlets and set permissions to executable:

I was able to install the IBM symphony rpm and run the postinstall scriptlet on my Slackware 12.1-ish box and I would like to package it up as a SlackBuild and also include the uninstall and update code from the .rpm file in the SlackBuild Package.

Thanks !

-- kjh

attached: get-rpm-scriptlets.txt ( save as get-rpm-scriptlets )

Attached Files

get-rpm-scriptlets.txt (3.1 KB, 23 views)

I would suggest just using the "rpm2tgz" program if you want to create a TGZ from an RPM. I am pretty sure it handles the pre- and post-scripts that run.

No it does not.

And the Slackware package format does not support uninstall-scripts anyway. The rpm post-install scriptlets can be added to Slackware's doinst.sh script and pre-install scripts are not supported at all.

Eric

indienick --

Does rpm2tgz extract the (pre and post) (install and uninstall) scriptlets from a .rpm and create the appropriate install.sh and (??? uninstall.sh ???) scripts ?

Looking at /usr/bin/rpm2targz, I don't see that functionality ... but then again <G> ...

See attached symphony-1.2-postinstall.txt script that I extracted from IBM's symphony-1.2.i586.rpm with get-rpm-scriptlets and ran after installing the package I extracted with rpm2tgz.

It created the proper symlinks and added symphony as an Item to my KDE 'Office' SubMenu.

What I would like to do is build a SlackBuild and include the uninstall scripts in the SlackBuild.

Thanks !

-- kjh

Attached Files

symphony-1.2-postinstall.txt (20.8 KB, 18 views)

"rpm2tgz" does not handle any scripts -it simply converts the archive to a tar.gz.

While a postinstall can be converted to a doinst.sh, installpkjg does not have any facility to run preinstall scripts. If there is something essential in there, you'd need to figure out how to run those commands on the package tree. Also, removepkg does not handl any sort of preuninstall or postuninstall scripts.

My src2pkg program might be helpful to convert the package to a proper slack-type package. It does a basic conversion or binary rpm's to tgz. And if you extract the postinstall and convert it to a doinst.sh, just place it alongside the rpm and src2pkg will automatically pick it up.

If you need to do anything else to the package content you can add custom commands to a src2pkg script to do that.
Just an idea....

gnashley --

Thanks for the pointer to src2pkg. Definitely worth checking out.

Alien Bob --

Thanks for the reply (! and many thanks for all the SlackBuild Packages you've shared with us the rest of us !) !

I suppose sharing an IBM symphony SlackBuild is a little iffy for now because the pre-install scriptlet does a bit of dependency checking and it also checks for install mode vs update mode ... I need to think about it for a while before releasing anything dangerous on the world ...

-- kjh

theoretically couldnt you just create a package within a package?
the initial slackware package would contain your preinstall script as a doinst.sh along with the binary package being placed in /tmp. at the end of doinst.sh have it execute an installpkg /tmp/<pkg>.tgz. the doinst.sh of that package would then contain all your postinstall stuff.

that's somewhat like how the open office autobuild slackware packages are set up isnt it?