public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] One-Day Gentoo Council Reminder for January 22
Date: Thu, 22 Jan 2009 17:02:33 +0000	[thread overview]
Message-ID: <20090122170233.1dab8ef7@snowcone> (raw)
In-Reply-To: <20090122165623.GA20446@comet>

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

On Thu, 22 Jan 2009 08:56:23 -0800
Donnie Berkholz <dberkholz@gentoo.org> wrote:
> Can this be fixed by adding bash dependencies to things using new 
> features? As long as we keep them out of the build path of bash,
> things ought to work.

Only if you're guaranteed bash 3.1 on boxes that do metadata
generation. Which means it won't work for overlays.

> Then we could add a repoman check for new features, if we wanted.

Can't do that unless you write a feature-complete bash parser and
pretend-execute every possible path an ebuild can take...

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-22 17:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 23:35 [gentoo-dev] One-Day Gentoo Council Reminder for January 22 Donnie Berkholz
2009-01-22  0:02 ` Donnie Berkholz
2009-01-22 16:15   ` Ciaran McCreesh
2009-01-22 17:23   ` Tobias Scherbaum
2009-01-22 17:38     ` Donnie Berkholz
2009-01-22 19:21     ` Ulrich Mueller
2009-01-22 19:47       ` Tobias Scherbaum
2009-01-22  3:28 ` Jeremy Olexa
2009-01-22  3:38   ` Donnie Berkholz
2009-01-22  4:10     ` Jeremy Olexa
2009-01-22 16:11       ` Ciaran McCreesh
2009-01-22 16:56         ` Donnie Berkholz
2009-01-22 17:02           ` Ciaran McCreesh [this message]
2009-01-22 17:12             ` Ciaran McCreesh
2009-01-22 17:28             ` Donnie Berkholz
2009-01-22 17:37               ` Ciaran McCreesh

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=20090122170233.1dab8ef7@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --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