From: Zac Medico <zmedico@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] PATCH: initial EAPI awareness
Date: Wed, 31 Aug 2005 05:30:06 -0700 [thread overview]
Message-ID: <4315A2CE.2060402@gmail.com> (raw)
In-Reply-To: <20050830123816.3f8cce27@andy.genone.homeip.net>
Marius Mauch wrote:
> On 08/30/05 Paul de Vrieze wrote:
>>I don't think it is a wise path to interpret EAPI's as integers at
>>all. There should not be guarantees of forward or backward
>>compatibility between versions. Interpreting them as integers seems
>>to imply that. Basically I think that EAPI could be anything wanted,
>>similar to SLOTS. Of course using digits is easy for humans.
>
>
> I've to agree with Paul here, portage should hold a list of all EAPI
> values it understands, not a maximum value.
>
I also agree. It seems like a list of string identifiers will give us a high level of forward flexibility.
For the implementation we can have a chain of EAPI handlers that are capable of determining whether or not they support a given EAPI. The first handler in the chain to accept the package will be allowed to handle it. Internally, these handlers may be able to share libraries and/or inherit from eachother.
Zac
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-31 12:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 10:53 [gentoo-portage-dev] PATCH: initial EAPI awareness Brian Harring
2005-08-28 5:46 ` Jason Stubbs
2005-08-28 9:29 ` Brian Harring
2005-08-28 15:32 ` warnera6
2005-08-28 9:31 ` Zac Medico
2005-08-28 9:45 ` Brian Harring
2005-08-29 8:32 ` Paul de Vrieze
2005-08-29 20:52 ` Zac Medico
2005-08-29 22:45 ` Brian Harring
2005-08-30 1:07 ` Brian Harring
2005-08-31 15:10 ` Zac Medico
2005-08-31 20:45 ` Brian Harring
2005-09-01 8:11 ` Zac Medico
2005-08-30 9:43 ` Paul de Vrieze
2005-08-30 10:38 ` Marius Mauch
2005-08-30 10:42 ` Brian Harring
2005-08-30 13:15 ` Marius Mauch
2005-08-30 13:28 ` Brian Harring
2005-08-30 14:47 ` Paul de Vrieze
2005-08-30 23:46 ` Brian Harring
2005-08-31 9:55 ` Paul de Vrieze
2005-08-31 12:58 ` Brian Harring
2005-08-31 14:59 ` Paul de Vrieze
2005-08-31 10:52 ` Marius Mauch
2005-08-31 12:57 ` Brian Harring
2005-08-31 14:43 ` Zac Medico
2005-08-31 15:41 ` Paul de Vrieze
2005-09-02 5:27 ` Zac Medico
2005-09-02 6:04 ` Brian Harring
2005-09-02 6:36 ` Zac Medico
2005-09-02 8:53 ` Paul de Vrieze
2005-09-02 12:27 ` Brian Harring
2005-09-02 8:42 ` Paul de Vrieze
2005-08-30 15:19 ` Marius Mauch
2005-08-31 12:30 ` Zac Medico [this message]
2005-09-02 6:31 ` Marius Mauch
2005-08-29 8:34 ` Brian Harring
2005-08-30 17:46 ` Marius Mauch
2005-08-30 23:38 ` Jason Stubbs
2005-08-31 0:12 ` Brian Harring
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=4315A2CE.2060402@gmail.com \
--to=zmedico@gmail.com \
--cc=gentoo-portage-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