Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: nostrip_files: allow full path
Date: Sat, 08 Jan 2022 17:51:55 +0100	[thread overview]
Message-ID: <20220108165155.-3OmyEt7hTe_AZdLT2NjBQ8syK77E-DAyIeUqAJUbDw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34886@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

There's a merged pull request on the void-packages repository

nostrip_files: allow full path
https://github.com/void-linux/void-packages/pull/34886

Description:
The option `nostrip_files` takes a filename without path, in contrast to
option `nopie_files` which takes only full path.

This is inconvenient in a case where there are two binaries with the
same name and only one must be stripped.

Case in point: maxima contains executables

    /usr/lib/maxima/5.45.1/binary-ecl/maxima
    /usr/lib/maxima/5.45.1/binary-sbcl/maxima

The second one breaks if stripped, but the first one is ok to strip (desirable: 59M -> 13M).

See: https://github.com/void-linux/void-packages/issues/34861#issuecomment-1006197772

This commit makes it so that `nostrip_files` can take either the
filename or the full path.



      parent reply	other threads:[~2022-01-08 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06  0:55 [PR PATCH] " tornaria
2022-01-08  1:26 ` [PR PATCH] [Updated] " tornaria
2022-01-08  1:28 ` tornaria
2022-01-08  1:29 ` [PR PATCH] [Updated] " tornaria
2022-01-08 16:51 ` Chocimier [this message]

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=20220108165155.-3OmyEt7hTe_AZdLT2NjBQ8syK77E-DAyIeUqAJUbDw@z \
    --to=chocimier@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).