public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] sys-apps/texinfo vs @system
Date: Mon, 1 Apr 2013 14:34:09 -0400	[thread overview]
Message-ID: <CAGfcS_kymLQJ9CZ2eXgO--1SOsNZGw+ZZa1VpgCGUU0_6vwhhQ@mail.gmail.com> (raw)
In-Reply-To: <201304011412.22990.vapier@gentoo.org>

On Mon, Apr 1, 2013 at 2:12 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> people seem happy with this, so i'll have the release team do a test build and
> see how it goes.

++

If any of the system packages are going to pull in texinfo then it
really should have a use flag for the perl-requiring parts.  Otherwise
we're not accomplishing much.  As already suggested all packages
should still install info files, and those who greatly care can
install mask them.

If while they're at it they can have the latest i686 and amd64 builds
not be hardened or nomultilib builds that would also be wonderful
(this issue has been coming up here and there for a few months now and
drives my automated scripts nuts).  :)

http://mirror.mcs.anl.gov/pub/gentoo/releases/amd64/autobuilds/latest-stage3-amd64.txt
http://mirror.mcs.anl.gov/pub/gentoo/releases/x86/autobuilds/latest-stage3-i686.txt

https://bugs.gentoo.org/show_bug.cgi?id=443472
https://bugs.gentoo.org/show_bug.cgi?id=463644

Rich


      reply	other threads:[~2013-04-01 18:34 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
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 [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=CAGfcS_kymLQJ9CZ2eXgO--1SOsNZGw+ZZa1VpgCGUU0_6vwhhQ@mail.gmail.com \
    --to=rich0@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