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 17:46:23 +0100 [thread overview]
Message-ID: <20221221164623.scQW6Zp8bE_13H1xcbxkrq1XSTqqmPSPOMeH1KtoWck@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: 926 bytes --]
New comment by malv-c on void-packages repository
https://github.com/void-linux/void-packages/issues/41204#issuecomment-1361657980
Comment:
not yet i have to install an other void os and extract your build
process from void-packages before
anyway i didn't ask for a downgrade in the distro yet
split docs and manpages sound horrible
...
Le mer. 21 déc. 2022 à 16:30, Michal Vasilek
***@***.***> a écrit :
>
> Do you have a comparison between packages built with each version? We will definitely not downgrade a core package like this just because one user prefers it. Void may not be the best choice for you, I think that the space saved by using an old version will be tiny if any and not splitting docs and manpages to subpackages will be a much bigger issue.
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID: ***@***.***>
prev parent reply other threads:[~2022-12-21 16:46 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
2022-12-21 15:30 ` paper42
2022-12-21 16:46 ` malv-c [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=20221221164623.scQW6Zp8bE_13H1xcbxkrq1XSTqqmPSPOMeH1KtoWck@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).