From: Dan Douglas <ormaaj@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bash-4.4 - call for testers
Date: Sat, 1 Oct 2016 11:34:43 -0500 [thread overview]
Message-ID: <CADVxHgP8cicYu3=w_EQY0AcMT0eF8v-Qb=X9HbA-X37EnjOpJg@mail.gmail.com> (raw)
In-Reply-To: <CAJnmqwbQnX1CG08HqOCY8D4nkoM+qvUfG0QjzjA3yehVcbeYMQ@mail.gmail.com>
On Sat, Oct 1, 2016 at 10:40 AM, konsolebox <konsolebox@gmail.com> wrote:
> I should also add that testing newer versions of bash becomes more
> risky sometimes, since bash would sometimes need a newer version of
> readline (see https://lists.gnu.org/archive/html/bug-bash/2016-09/msg00020.html).
> Rebuilding or installing a newer version of readline would cause some
> other packages that depend on it to be rebuilt as well.
>
> If bash and readline become multi-slotted (or shared if there's a
> difference), it would be easier to test them. Other stuff would also
> not need to be rebuilt immediately.
AFAIK upstream doesn't technically support unbundled readline anyway. If
newer readline isn't tested with older bashes it would be miraculous
for it to be backwards-compatible with every bash version in the tree.
I'd be perfectly happy requiring bundled readline when USE="readline"
for bash versions incompatible with the installed readline, or simply
depending on USE="-readline" for those versions. I rarely if ever use
interactive mode with anything other than my system default /bin/bash.
next prev parent reply other threads:[~2016-10-01 16:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 11:41 [gentoo-dev] bash-4.4 - call for testers Lars Wendler
2016-09-22 9:22 ` David Haller
2016-09-23 10:42 ` David Haller
2016-09-29 5:54 ` Dan Douglas
2016-09-29 21:56 ` Andy Mender
2016-09-29 22:29 ` Kent Fredric
2016-09-30 13:38 ` William Hubbs
2016-09-30 17:09 ` Andy Mender
2016-10-01 6:59 ` Dan Douglas
2016-10-01 7:47 ` Dan Douglas
2016-09-30 17:53 ` konsolebox
2016-09-30 17:49 ` konsolebox
2016-10-01 0:38 ` Kent Fredric
2016-10-01 14:38 ` konsolebox
2016-10-01 15:40 ` konsolebox
2016-10-01 16:34 ` Dan Douglas [this message]
2016-10-02 5:28 ` konsolebox
2016-10-02 5:40 ` Kent Fredric
2016-10-02 8:03 ` konsolebox
2016-10-02 8:58 ` Kent Fredric
2016-10-02 10:00 ` konsolebox
2016-10-02 10:18 ` konsolebox
2016-10-02 11:42 ` Kent Fredric
2016-10-03 5:32 ` konsolebox
2016-10-03 5:37 ` konsolebox
2016-10-03 5:47 ` konsolebox
2016-10-03 5:53 ` Kent Fredric
2016-10-03 6:37 ` konsolebox
2016-10-03 7:09 ` Kent Fredric
2016-10-03 12:02 ` konsolebox
2016-10-02 6:29 ` konsolebox
2016-10-01 21:48 ` Dan Douglas
2016-10-01 22:40 ` Dan Douglas
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='CADVxHgP8cicYu3=w_EQY0AcMT0eF8v-Qb=X9HbA-X37EnjOpJg@mail.gmail.com' \
--to=ormaaj@gmail.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