public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: sys-apps/texinfo vs @system
Date: Mon, 1 Apr 2013 14:10:30 -0400	[thread overview]
Message-ID: <201304011410.31048.vapier@gentoo.org> (raw)
In-Reply-To: <pan$527de$b390106$9b81857f$775e3a08@cox.net>

[-- Attachment #1: Type: Text/Plain, Size: 1210 bytes --]

On Sunday 31 March 2013 05:19:58 Duncan wrote:
> Mike Frysinger posted on Sun, 31 Mar 2013 01:59:52 -0400 as excerpted:
> > it'd be simpler if we just dropped [texinfo] 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).
> 
> Except... at least for those running build-systems, some of those <100
> pkgs with hard deps on texinfo include automake, autoconf, gcc, and
> e2fsprogs, all of which are pretty core to a gentoo system, at least one
> that builds anything.

any core package that includes info pages should not be regenerating them 
hence should not need texinfo.  i've applied a fix already for gcc to do just 
that.

we've already dropped autoconf/automake from @system since the autotools 
eclass handles that for us.

other packages might need more work along the same way.

> Texinfo may be more practical to remove on binpkg-only systems, tho,
> which might be what you had in mind, but if there was hint of that I
> didn't catch it.

binpkg or custom ROOTs.  both are important to me.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-04-01 18:10 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 [this message]
2013-03-31 21:42 ` [gentoo-dev] " Anthony G. Basile
2013-03-31 22:07 ` Doug Goldstein
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=201304011410.31048.vapier@gentoo.org \
    --to=vapier@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