public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: bash version in ebuilds/eclasses...non-compliance and what to do?
Date: Sat, 20 Dec 2008 10:42:34 +0100	[thread overview]
Message-ID: <20081220094233.GA1272@gentoo.org> (raw)
In-Reply-To: <gii0m0$e8f$1@ger.gmane.org>

On 20-12-2008 05:35:25 +0000, Steve Long wrote:
> I note that bash-3.2_p17-r1 is stable on all the architectures that 3.0-r12
> lists (it just adds the two -fbsd archs as unstable.) portage-2.1.4.5
> requires at least that version (only unstable on mips as against 2.1.1-r2)
> It might be worth skipping to 3.2, since that would simplify regex handling.

The only problem we have there is that bash-3.2.17 only comes in patches
on top of 3.2.  During bootstrap that's problematic, as gnu patch (or
any other patch) might not be available, or simply b0rked.
For that reason we bootstrap with a portage pre SVN revision 10460,
which does not require >=3.2.17.
See http://bugs.gentoo.org/show_bug.cgi?id=229677#c11 on why PMS should
require 3.2.17 over plain 3.2 if you decide to push the requirement
update.

We can work around it by using a self-made pre-patched tarball, though.


-- 
Fabian Groffen
Gentoo on a different level



  reply	other threads:[~2008-12-20  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 23:46 [gentoo-dev] bash version in ebuilds/eclasses...non-compliance and what to do? Jeremy Olexa
2008-12-20  5:35 ` [gentoo-dev] " Steve Long
2008-12-20  9:42   ` Fabian Groffen [this message]
2008-12-24 11:31     ` [gentoo-dev] " Steve Long
2008-12-20 13:54   ` [gentoo-dev] " Ciaran McCreesh
2010-01-15  5:34 ` [gentoo-dev] " Mike Frysinger
2010-01-15 10:46   ` Fabian Groffen
2010-01-15 15:13   ` [gentoo-dev] " Christian Faulhammer

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=20081220094233.GA1272@gentoo.org \
    --to=grobian@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