From: malv-c <malv-c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: binutils-2.35.Package request:
Date: Wed, 21 Dec 2022 10:10:18 +0100 [thread overview]
Message-ID: <20221221091018.VHI1cmC8Nh34VPTf7O_S7UqtrsxXgzZMk-xvJwYhdH8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41204@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
New comment by malv-c on void-packages repository
https://github.com/void-linux/void-packages/issues/41204#issuecomment-1361044956
Comment:
re
as i wrote 2.35 give smaller binary executables
as i want to rebuild all packages with -Os -flto and elses then sstrip of
https://github.com/BR903/ELFkickers to remove unused space on it before
install on my devices
as you wrote that in void-packages individual packages are not handled the
issue is on the design...
thanks Michael
Le mer. 21 déc. 2022 à 09:02, Michal Vasilek ***@***.***> a
écrit :
> Could you explain why you want void-packages to downgrade binutils to
> 2.35? Every single package seems to build and work fine and it is part of
> the toolchain, so I am not sure that's even possible. We definitely do not
> want to do it without a very good reason.
> I am not sure what you want void-packages to document. Documenting
> reverting a commit and checking out at a specific commit hash is not in
> scope of void-packages and fixing all of the other packages to properly
> work with the old version is not something that can be documented.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/41204#issuecomment-1360975875>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AESIHJMCU5YP4KDX25DJQGLWOK2QXANCNFSM6AAAAAATEWHX6E>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
next prev parent reply other threads:[~2022-12-21 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 16:37 [ISSUE] " malv-c
2022-12-20 21:36 ` paper42
2022-12-20 21:36 ` [ISSUE] [CLOSED] " paper42
2022-12-21 7:41 ` malv-c
2022-12-21 8:02 ` paper42
2022-12-21 9:10 ` malv-c [this message]
2022-12-21 15:30 ` paper42
2022-12-21 16:46 ` malv-c
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=20221221091018.VHI1cmC8Nh34VPTf7O_S7UqtrsxXgzZMk-xvJwYhdH8@z \
--to=malv-c@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).