You are right. As you said, only the symbolic link is put in the package. For the SVR4 to RPM conversion, I guess the links need to be constructed under the BuildRoot before calling 'rpmbuild'. This is little troublesome but manageable.
Thanks again.
-Kamal
Jos Vos wrote:
On Wed, Jun 02, 2004 at 01:29:45PM -0500, Kamal Hussain wrote:
If I have a soft link in the build root, it looks like RPM resolves it and pulls in the actual file to the package but this is not what I want rather I want to defer the linking to the installation time.
If there is a symlink in the buildroot, (only) that symlink is put in the final package. I'm very sure, I use it all the time, so if you saw something different, something went wrong there.
If you want to convert those package specifications, you should create (in this example) symlinks test1 and test2 in the buildroot and include all three (test, test1 and test2) in the %files section, without any further difference, and this should have the desired effect (test is a "real file" and test1 and test2 are symlinks).
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
