Upgrade of custom package removes symlink

Here's my predicament. I am certain there is a workaround in the RPM
package creation process.

I am responsible for creating RPM packages for a proprietary product
that does not support RPM. I performed a standard install of the
software as per their instructions. It requires user-interaction but
installs to a single directory.
However, the final install creates a symlink from the target install
directory, i.e.
ln -s /usr/local/product /product.
However, prior to my arrival here, the previous release had as part of
its SPEC file the following section in %postun.
rm -f /product
Now, when I use the up2date option, version 6.5 is downloaded and
installed and the symlink created. But then up2date uninstalls version
5.5 and removes the /product symlink. This symlink is required in order
for said product to run. Up2date is what my company uses for updating
RPMs throughout the business.

Any ideas on how I can retain the /product symlink to
/usr/local/product when using the up2date option?
Just wondering if there is any other option I can add to the
product.spec file that would help retain this link even after upgrade.
I have tested several different options including forcing the creation
of the symlink in the %post section, and verifying a symlink exists in
the %pre and %install sections.
I have gone to the vendor and they were no help and said they would not
support any product specific packages.
Thanks.
KJ

linux.redhat.rpm wrote:

> Any ideas on how I can retain the /product symlink to
> /usr/local/product when using the up2date option?

I think you would need to use SELinux (Kernel that uses the patches for
increased security from NSA) and deny root from modify /product.


> Just wondering if there is any other option I can add to the
> product.spec file that would help retain this link even after upgrade.
> I have tested several different options including forcing the creation
> of the symlink in the %post section, and verifying a symlink exists in
> the %pre and %install sections.
> I have gone to the vendor and they were no help and said they would not
> support any product specific packages.

The only other option I can think of, would be setup a private up2date server,
where you fetch the packages needed, but the package in question you only
fetch the source-rpm, you then have a script that will rebuild the package
after you patched the spec file and remove the line "rm -f /product".

Then all the company computers can update against the private server, this way
you get around the problem, but you will have the work of creating the script
that will automatically make the new rpm without the removal of the symlink.


There is the option --noscripts for rpm, but this can cause other problems
(see the man page: man rpm), not sure if up2date allows you to set rpm options
for specific packages.


//Aho