Re: For a cross-compiling toolchain, does it matter if /usr/bin/* links are symbolic or hard?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/12/2015 04:46 PM, Ralf Corsepius wrote:
On 11/12/2015 04:36 PM, Nico Kadel-Garcia wrote:
On Thu, Nov 12, 2015 at 4:11 AM, Jonathan Dieter <jdieter@xxxxxxxxx>
wrote:
I'm reviewing nacl-binutils (https://bugzilla.redhat.com/show_bug.cgi?i
d=1270355), which has hard links from /usr/x86_64-nacl/* to
/usr/bin/x86_64-nacl-*.  According to https://fedoraproject.org/wiki/Pa
ckaging_Cross_Compiling_Toolchains, these should be symlinks, and
rpmlint complains about cross-directory-hard-links.  Is there any
reason to convert these to symlinks or can we just leave them as hard
links?

Thanks,
Jonathan

Thereis is, generally, no good excuse for a hardlink in an RPM. The
symlinks help indicate where the component actually resides,
Things are not so clear as you think.

May-by are in a position to tell where a cross-gcc|as|ar|ld recides?

Though I have been an active contributor/maintainer to binutils and gcc
for ca. a decade, I am not. The different locations are different views
at identical binaries, aiming at different use-cases.

Also, these links exist for very long times (>> 15 years) and have
never, ever been a problem.

FWIW: Even on Debian, these are hardlinks.

Ralf


--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux