I guess the answer is that there is no special flags required to denote a symlink. All files could go under %files block and during the package creation, RPM will determine which files are softlinks. This of course requires all the soft links to be created before building the package and it can be done either using %prep , %install directives or outside the RPM.
The approach is very different from that of SVR4.. I would say SVR4 is more advanced in this aspect because you can specify softlinks without creating them during the packaging phase..
-Kamal
David Lim wrote:
Asking the question another way, I use
%files -f all.lst
What entry do I put in all.lst to specify a symlink?
"JV" == Jos Vos <jos@xxxxxx> writes:
JV> On Wed, Jun 02, 2004 at 02:46:10PM -0500, Kamal Hussain wrote:
>> 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.
JV> Well, they should be created in the %install section of the spec file JV> (I guess you convert a SVR4 specification to a RPM spec file):
JV> %install JV> ... JV> fill the buildroot with real files JV> ...
JV> ln -s test $RPM_BUILD_ROOT/usr/bin/test1 JV> ln -s test $RPM_BUILD_ROOT/usr/bin/test2
JV> (or something similar)
JV> -- JV> -- Jos Vos <jos@xxxxxx>
JV> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
JV> -- Amsterdam, The Netherlands | Fax: +31 20 6948204
JV> _______________________________________________ JV> Rpm-list mailing list JV> Rpm-list@xxxxxxxxxx JV> https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
