Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ciaran McCreesh <ciaran.mccreesh@...>
Subject: Re: My wishlist for EAPI 5
Date: Wed, 20 Jun 2012 22:10:05 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 20 Jun 2012 17:02:10 -0400
Richard Yao <ryao@g.o> wrote:
> >> 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.
> > 
> 
> Source the ebuild using the system shell, check for WANT_SH. If it
> does not exist, proceed. If it does, start over with a different
> shell.
> 
> I do not see any technical problem.

Package managers don't "source the ebuild"... You should take a look at
the amount of horrible bash code the three PMs have, and see why it's
there.

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

iEYEARECAAYFAk/iPC8ACgkQ96zL6DUtXhH6rQCghGeOb2N8iOm9F5u7k9jJkn2s
hcwAoKLB4kSHq7KaVh9D7mllQnU3U78Z
=DLvZ
-----END PGP SIGNATURE-----
References:
My wishlist for EAPI 5
-- Richard Yao
Re: My wishlist for EAPI 5
-- Ciaran McCreesh
Re: My wishlist for EAPI 5
-- Richard Yao
Re: My wishlist for EAPI 5
-- Ciaran McCreesh
Re: My wishlist for EAPI 5
-- Richard Yao
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: My wishlist for EAPI 5
Next by thread:
Re: My wishlist for EAPI 5
Previous by date:
Re: Killing UEFI Secure Boot
Next by date:
Re: My wishlist for EAPI 5


Updated Jun 28, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.