public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Luca Barbato <lu_zero@gentoo.org>
Cc: gentoo-council@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: Re: Issues regarding glep-55  (Was: [gentoo-council] Re: Preliminary Meeting-Topics for 12 February 2009)
Date: Mon, 23 Feb 2009 13:57:02 +0000	[thread overview]
Message-ID: <20090223135702.3d593d3f@snowcone> (raw)
In-Reply-To: <49A206A7.3050604@gentoo.org>

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

On Mon, 23 Feb 2009 03:15:03 +0100
Luca Barbato <lu_zero@gentoo.org> wrote:
> Let's try to start with a common workflow for the user:
> - an user with an ancient version of portage syncs
> - it requires a package
> - it looks at the cache ($portdir/metadata/cache/)
> - picks the best entry from the ones showing an eapi it understands
> - keeps going.
> 
> Apparently we do not have any issue...

...assuming the metadata cache is valid. That isn't always the case.

> 2- The user will get unpredictable behavior, but portage tell you
> when upgrading is needed...

Not if the version you'd need to do metadata generation is ~arch it
doesn't.

> 3- you'd have to disable them

Yes, tell everyone to disable all the overlays that make use of a few
features only in ~arch package managers... That'll work...

> In this case we have a problem if the source step is a single one, 
> portage won't know in advance how to behave.
> 
> So the first step has to be split in two:
> - first portage discovers which is the eapi version

...which it can't do, because it doesn't know the EAPI.

> The problem is that right now sourcing is done by having an
> instructed bash. So the simplest way to get the first step done is
> parsing the ebuild file with something different like file(1) and
> then instruct bash and do the parsing.

file(1) can't parse ebuilds. Only an ebuild implementation can parse
ebuilds, and only if it already knows the EAPI.

> What is proposed in glep-55 seems to aim to solve both issues at the 
> same time (it isn't stated) by switching file extension every time
> the eapi is changed. This is slightly against the principle of the
> least surprise and apparently is disliked by enough people to lead
> the situation to be discussed in the council.

There's no surprise at all. It's extremely clear.

-- 
Ciaran McCreesh

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

  parent reply	other threads:[~2009-02-23 13:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  9:12 [gentoo-council] Preliminary Meeting-Topics for 12 February 2009 Tiziano Müller
2009-02-10 21:25 ` Donnie Berkholz
2009-02-12  6:53   ` Tiziano Müller
2009-02-12 15:50     ` Donnie Berkholz
2009-02-12 15:55       ` Ciaran McCreesh
2009-02-12 16:01         ` Donnie Berkholz
2009-02-12 16:12           ` Ciaran McCreesh
2009-02-12 17:28             ` Donnie Berkholz
2009-02-12 16:47           ` Tiziano Müller
2009-02-12 17:20             ` Donnie Berkholz
2009-02-10 23:11 ` [gentoo-council] Website changes [WAS] " Donnie Berkholz
2009-02-11 15:51   ` Tiziano Müller
2009-02-11 19:19     ` Donnie Berkholz
2009-02-11 20:01       ` Luca Barbato
2009-02-10 23:13 ` [gentoo-council] GSoC results from 2008 " Donnie Berkholz
2009-02-12  5:48   ` Alec Warner
2009-02-12 14:53 ` [gentoo-council] " Tiziano Müller
2009-02-12 16:00   ` Donnie Berkholz
2009-02-12 16:16     ` Donnie Berkholz
2009-02-12 16:21       ` Ciaran McCreesh
2009-02-12 17:10         ` Donnie Berkholz
2009-02-12 17:21           ` Ciaran McCreesh
2009-02-12 17:37             ` Donnie Berkholz
2009-02-12 18:03               ` Ciaran McCreesh
2009-02-12 19:01                 ` Alistair Bush
2009-02-12 19:08                   ` Ciaran McCreesh
2009-02-12 19:54                   ` Luca Barbato
2009-02-12 20:01                     ` Ciaran McCreesh
2009-02-19 10:06                 ` Peter Volkov
2009-02-19 12:51                   ` Ciaran McCreesh
2009-02-19 13:30                     ` Luca Barbato
2009-02-19 15:23                       ` Ciaran McCreesh
2009-02-19 21:11                     ` Peter Volkov
2009-02-19 21:21                       ` Ciaran McCreesh
2009-02-22 23:16                       ` [gentoo-council] " Ryan Hill
2009-02-22 23:37                         ` Luca Barbato
2009-02-22 23:48                           ` Ciaran McCreesh
2009-02-23  2:15                             ` Issues regarding glep-55 (Was: [gentoo-council] Re: Preliminary Meeting-Topics for 12 February 2009) Luca Barbato
2009-02-23  8:38                               ` Tiziano Müller
2009-02-23 13:21                                 ` [gentoo-dev] " Luca Barbato
2009-02-23 13:40                                   ` Thomas Anderson
2009-02-23 13:57                               ` Ciaran McCreesh [this message]
2009-02-23 14:46                                 ` Luca Barbato
2009-02-23 14:59                                   ` 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=20090223135702.3d593d3f@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=lu_zero@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