Let me clarify it again. In SVR4, you can have following specifications in the prototype file
f none /bin/test l none /bin/test1=test l none /bin/test2=test
During the installation of the package, /bin/test will be installed and test1 & test2 files will be created as soft links to /bin/test file.
Basically, I am trying to automate conversion of SVR4 packages to RPM and couldn't find an easy way to convert special files like softlinks.
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.
Thanks Kamal
Jos Vos wrote:
On Wed, Jun 02, 2004 at 12:25:50PM -0500, Kamal Hussain wrote:
I am looking for an SVR4 equivalent functionality of specifying the soft links in the RPM package. SVR4 allows something called "ftype" (in the prototype file) which can take variety of values like f, e, d, s etc to mark the contents of a package into file types like linked file, Named pipe, character special device and soft link.
Not sure if I understand your question right, but: RPM just takes the file type as it appears in the buildroot (if it's a character special file or symlink in the buildroot, it is a character special file or symlink in the final package, for example) and you can override permissions and owner/group in the %files section, if you want.
AFAIK it is not possible to completely override a file type, if it does not appear as such in the buildroot.
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
