Github messages for voidlinux
 help / color / mirror / Atom feed
From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: binutils: remove dependency to binutils-doc
Date: Tue, 04 May 2021 20:46:38 +0200	[thread overview]
Message-ID: <20210504184638.vnZHCH9EdkawKV2hVnpxtxySZajoTBzV3Ur370pPC-I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30678@inbox.vuxu.org>

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

New comment by ailiop-git on void-packages repository

https://github.com/void-linux/void-packages/pull/30678#issuecomment-832163568

Comment:
So I agree with folding it into the main package, if we are to follow the manual guideline given that the size of the docs is the deciding factor (we do have other packages with tiny docs split off into a subpkg, e.g. 66, which probably need fixing).

I'm assuming that the original reason was so that the cross binutils can share the doc, but they certainly don't depend on it (so we probably better remove the depends from them). Both cross-arm-none-eabi-binutils and cross-or1k-none-elf-binutils rm the info files at the post_install phase so there should be no conflict.

What do you think?

  parent reply	other threads:[~2021-05-04 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 18:16 [PR PATCH] " ailiop-git
2021-05-04 18:18 ` ericonr
2021-05-04 18:19 ` ericonr
2021-05-04 18:24 ` ericonr
2021-05-04 18:46 ` ailiop-git [this message]
2021-05-04 19:32 ` ericonr
2021-05-04 19:33 ` ericonr
2022-05-19  2:16 ` github-actions
2022-06-03  2:11 ` [PR PATCH] [Closed]: " github-actions

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=20210504184638.vnZHCH9EdkawKV2hVnpxtxySZajoTBzV3Ur370pPC-I@z \
    --to=ailiop-git@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).