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] My wishlist for EAPI 5
Date: Wed, 20 Jun 2012 21:54:04 +0100	[thread overview]
Message-ID: <20120620215404.2497aa28@googlemail.com> (raw)
In-Reply-To: <4FE23799.5080003@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 20 Jun 2012 16:50:33 -0400
Richard Yao <ryao@gentoo.org> wrote:
> On 06/20/2012 04:35 PM, Ciaran McCreesh wrote:
> > On Wed, 20 Jun 2012 16:25:30 -0400 Richard Yao <ryao@gentoo.org>
> > wrote:
> >> Multilib (and/or multiarch) support The current binaries cause a
> >> great deal of pain, particularly when a user does not want to
> >> upgrade something. I had this problem with WINE and glibc because
> >> I wanted to avoid the reverse memcpy() fiasco on my systems. This
> >> situation would have been avoided entirely if the package manager
> >> supported multilib.
> > 
> > This one's unlikely to happen unless someone's prepared to put in
> > the work.
> 
> The multilib-portage overlay already has this working.

But there is no spec, nor is there a developer-centric description of
it.

> > So far as I know, every PM relies heavily upon bash anyway (and
> > can't easily be made not to), so even if developers would accept
> > having to rewrite all their eclasses, it still wouldn't remove the
> > dep.
> 
> Lets address POSIX compliance in the ebuilds first. Then we can deal
> with the package managers.

Why? It's highly doubtful the package manglers could switch shells even
if they wanted to, and even if every ebuild started using EAPI 5. It's
wasted effort.

- -- 
Ciaran McCreesh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/iOG8ACgkQ96zL6DUtXhG5FgCgw3V9qz3o1d0A4TUw5y83lfCE
LWkAnRbY4WKJz1xribnhUat0YL1XEwHR
=dYt+
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-06-20 20:58 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 20:25 [gentoo-dev] My wishlist for EAPI 5 Richard Yao
2012-06-20 20:35 ` Ciaran McCreesh
2012-06-20 20:50   ` Richard Yao
2012-06-20 20:54     ` Ciaran McCreesh [this message]
2012-06-20 21:02       ` Richard Yao
2012-06-20 21:10         ` Ciaran McCreesh
2012-06-20 21:05       ` Richard Yao
2012-06-20 21:12         ` Ciaran McCreesh
2012-06-20 21:34           ` Richard Yao
2012-06-21  8:29     ` [gentoo-dev] " Duncan
2012-06-21  9:23       ` Richard Yao
2012-06-22  0:38       ` Richard Yao
2012-06-22  5:30         ` Duncan
2012-06-22  5:55         ` Michał Górny
2012-06-22  6:20         ` Ben de Groot
2012-06-20 21:43   ` [gentoo-dev] " Justin
2012-06-21  6:08     ` Pacho Ramos
2012-06-21  7:00       ` Ciaran McCreesh
2012-06-21  7:25         ` Pacho Ramos
2012-06-21  7:39           ` Ciaran McCreesh
2012-06-23  7:53             ` Pacho Ramos
2012-06-23  9:38               ` Ciaran McCreesh
2012-06-23  9:53                 ` Peter Stuge
2012-06-23 10:24                   ` Pacho Ramos
2012-06-23 10:30                     ` Pacho Ramos
2012-06-23 10:31                     ` Ciaran McCreesh
2012-06-23 11:05                       ` Pacho Ramos
2012-06-23 11:14                         ` Ciaran McCreesh
2012-06-23 11:38                           ` Peter Stuge
2012-06-23 11:37                             ` Ciaran McCreesh
2012-06-23 11:52                               ` Peter Stuge
2012-06-23 11:59                                 ` Ciaran McCreesh
2012-06-23 12:16                                   ` Pacho Ramos
2012-06-23 12:21                                     ` Ciaran McCreesh
2012-06-23 12:11                               ` Pacho Ramos
2012-06-23 12:16                                 ` Ciaran McCreesh
2012-06-23 12:33                                   ` Pacho Ramos
2012-06-23 10:37                 ` [gentoo-dev] " Duncan
2012-06-23 10:43                   ` Duncan
2012-06-23 10:44                   ` Ciaran McCreesh
2012-06-23 11:12                     ` Rich Freeman
2012-06-23 23:09                       ` Duncan
2012-06-21  9:27           ` [gentoo-dev] " Alec Warner
2012-06-21 12:04             ` Rich Freeman
2012-06-23  8:19             ` Pacho Ramos
2012-06-21 11:15           ` Patrick Lauer
2012-06-21 11:37             ` Ciaran McCreesh
2012-06-23  8:01             ` Pacho Ramos
2012-06-21 12:11         ` Homer Parker
2012-06-21 12:30           ` Ciaran McCreesh
2012-06-21 13:13             ` Homer Parker
2012-06-21 13:20               ` Ciaran McCreesh
2012-06-21 20:26                 ` Homer Parker
2012-06-21 22:46                   ` Rich Freeman
2012-06-29  5:27           ` Mike Frysinger
2012-06-29  5:29         ` Mike Frysinger
2012-06-21  6:41     ` Ciaran McCreesh
2012-06-21  7:24       ` justin
2012-06-21 12:14         ` Homer Parker
2012-06-21 12:38           ` Ciaran McCreesh
2012-06-20 20:39 ` Maxim Kammerer
2012-06-20 20:41   ` Ciaran McCreesh
2012-06-20 20:51   ` Richard Yao
2012-06-29  5:20   ` Mike Frysinger
2012-06-20 20:52 ` Luca Barbato
2012-06-20 21:33 ` Alec Warner
2012-06-21  9:42   ` Ben de Groot
2012-06-29  5:25 ` Mike Frysinger

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=20120620215404.2497aa28@googlemail.com \
    --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