public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] sys-apps/texinfo vs @system
Date: Sun, 31 Mar 2013 17:07:19 -0500	[thread overview]
Message-ID: <CAFWqQMQTABx0em4RU5oQGf9b3YyPJci-03YrOpQVLoRFLGJt2g@mail.gmail.com> (raw)
In-Reply-To: <201303310159.53246.vapier@gentoo.org>

On Sun, Mar 31, 2013 at 12:59 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> the new texinfo-5.x series has rewritten makeinfo in perl.  the main `info`
> program is still in pure C.
>
> when it comes to packages installing .info pages, it's largely limited to the
> GNU projects as the format has never really caught on.  many of those projects
> also install man pages.
>
> personally, i've never found info pages usable.  for most utils, the man pages
> or the --help output is sufficient, and for people doing heavy development, the
> online html manuals are significantly more useful.

agreed.

>
> when it was pure C, i could live with it as it's only <1MiB and no real deps
> to speak of.  now it's more like 3MiB, and pulls in 3 semi-uncommon additional
> perl packages (not to mention perl itself).
>
> it's in @system for two reasons: it provides `info` and `makeinfo`.  the
> former is for reading info pages (i.e. RDEPEND) while the latter is used for
> generating info pages (i.e. DEPEND) when the tarball didn't ship with them
> pregenerated (they usually do).
>
> one option would be to make the makeinfo stuff into a USE flag so all the perl
> junk isn't pulled in by default.  only the packages that actually generate
> info pages can DEPEND on that.
>
> it'd be simpler if we just dropped it altogether from @system.  if people want
> `info`, they can `emerge` it themselves.  if packages want `makeinfo`, they
> can DEPEND on it -- few fall into this category (<100 by a rough survey of
> random Gentoo installs).
>
> obviously my preference is for the latter.
> -mike

I agree with the later as well.

-- 
Doug Goldstein


  parent reply	other threads:[~2013-03-31 22:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31  5:59 [gentoo-dev] sys-apps/texinfo vs @system Mike Frysinger
2013-03-31  9:19 ` [gentoo-dev] " Duncan
2013-03-31 10:19   ` Ulrich Mueller
2013-03-31 22:08     ` Michael Mol
2013-04-01 18:10   ` Mike Frysinger
2013-03-31 21:42 ` [gentoo-dev] " Anthony G. Basile
2013-03-31 22:07 ` Doug Goldstein [this message]
2013-03-31 22:12 ` Diego Elio Pettenò
2013-04-01  8:02 ` [gentoo-dev] " Michael Palimaka
2013-04-01 18:12 ` [gentoo-dev] " Mike Frysinger
2013-04-01 18:34   ` Rich Freeman

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=CAFWqQMQTABx0em4RU5oQGf9b3YyPJci-03YrOpQVLoRFLGJt2g@mail.gmail.com \
    --to=cardoe@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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