From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] util-linux: Do not ship broken symlink "/usr/bin/x86_64"
Date: Tue, 12 Jul 2022 12:00:45 +0200 [thread overview]
Message-ID: <9EDD4D00-5DB1-43D4-8E88-7DCB0829F276@ipfire.org> (raw)
In-Reply-To: <5f1428c8-54aa-140e-0779-8f5a63be1977@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
Oh no, we should of course ship setarch or drop x86_64. Either or the other.
I missed that we were talking about a *broken* symlink here.
> On 12 Jul 2022, at 11:44, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello Michael,
>
> thanks for your reply.
>
>> Hello,
>>
>> Err, yes, but what do we gain from dropping this?
>
> Well, shipping a broken symlink did not seem to serve any purpose to me. Or were
> you referring to not shipping /usr/bin/setarch?
>
> Thanks, and best regards,
> Peter Müller
>
>>
>> Does it hurt us to be compatible with any general purpose distribution?
>>
>> -Michael
>>
>>> On 9 Jul 2022, at 14:37, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>>
>>> This file points to /usr/bin/setarch, which we do not ship on any
>>> architecture. As it serves no obvious purpose on IPFire installations,
>>> we may as well not ship it entirely.
>>>
>>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>>> ---
>>> config/rootfiles/common/x86_64/util-linux | 2 +-
>>> config/rootfiles/core/170/update.sh | 1 +
>>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/config/rootfiles/common/x86_64/util-linux b/config/rootfiles/common/x86_64/util-linux
>>> index bd862b557..de78f65c2 100644
>>> --- a/config/rootfiles/common/x86_64/util-linux
>>> +++ b/config/rootfiles/common/x86_64/util-linux
>>> @@ -103,7 +103,7 @@ usr/bin/uclampset
>>> usr/bin/uuidgen
>>> usr/bin/uuidparse
>>> #usr/bin/whereis
>>> -usr/bin/x86_64
>>> +#usr/bin/x86_64
>>> #usr/include/blkid
>>> #usr/include/blkid/blkid.h
>>> #usr/include/libfdisk
>>> diff --git a/config/rootfiles/core/170/update.sh b/config/rootfiles/core/170/update.sh
>>> index e3f93df57..5d8903189 100644
>>> --- a/config/rootfiles/core/170/update.sh
>>> +++ b/config/rootfiles/core/170/update.sh
>>> @@ -57,6 +57,7 @@ rm -rvf \
>>> /sbin/ifcfg \
>>> /sbin/routef \
>>> /sbin/rtpr \
>>> + /usr/bin/x86_64 \
>>> /usr/lib/libbfd-2.36.* \
>>> /usr/lib/libbind9-9.16.2* \
>>> /usr/lib/libdnet* \
>>> --
>>> 2.35.3
>>
next prev parent reply other threads:[~2022-07-12 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:37 Peter Müller
2022-07-09 14:30 ` Adolf Belka
2022-07-11 13:02 ` Peter Müller
2022-07-11 17:02 ` Michael Tremer
2022-07-12 9:44 ` Peter Müller
2022-07-12 10:00 ` Michael Tremer [this message]
2022-07-12 10:42 ` Peter Müller
2022-07-12 11:21 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9EDD4D00-5DB1-43D4-8E88-7DCB0829F276@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox