public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Andrew D Kirch <trelane@trelane.net>
Cc: Ulrich Mueller <ulm@gentoo.org>,
	Patrick Lauer <patrick@gentoo.org>,
	gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] tree-layout.tex small cleanup
Date: Sat, 19 Sep 2009 23:38:49 +0100	[thread overview]
Message-ID: <20090919233849.1d7713f3@snowmobile> (raw)
In-Reply-To: <4AB55BBA.9070908@trelane.net>

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

On Sat, 19 Sep 2009 18:31:22 -0400
Andrew D Kirch <trelane@trelane.net> wrote:
> > But it was an official Gentoo project, and it was used in a
> > repository run by the Gentoo KDE team. Remember that EAPI support
> > is needed to be able to uninstall a package that was installed with
> > a particular EAPI, so EAPIs can't be removed even when they're no
> > longer in use.
>
> I can't agree here.  While no process exists to remove deprecated EAPI
> functionality, this sort of thing should be noted in the NEXT EAPI
> RELEASED and via that method eliminated.

Please explain what you mean. EAPIs are conceptually independent, and
don't deprecate each other in any kind of way, and future EAPI
releases can't retroactively change what previous EAPIs said.

> This is a specifications document, not a history lesson covering past
> mistakes.

Getting off-topic here, but which parts of kdebuild-1 do you think were
mistakes? Given how kdebuild-1 features are making their way into EAPIs
2, 3 and beyond as Portage gains support for them, I'm sure you don't
mean that every feature was wrong, so which of the remaining ones do you
think shouldn't be adopted and why?

-- 
Ciaran McCreesh

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

  reply	other threads:[~2009-09-19 22:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 20:15 [gentoo-pms] tree-layout.tex small cleanup Patrick Lauer
2009-09-19 20:25 ` Ciaran McCreesh
2009-09-19 20:34   ` Patrick Lauer
2009-09-19 20:45     ` Ciaran McCreesh
2009-09-19 20:56       ` Patrick Lauer
2009-09-19 21:08         ` Ciaran McCreesh
2009-09-19 22:03       ` Ulrich Mueller
2009-09-19 22:11         ` Ciaran McCreesh
2009-09-19 22:31           ` Andrew D Kirch
2009-09-19 22:38             ` Ciaran McCreesh [this message]
2009-09-19 23:19               ` Andrew D Kirch
2009-09-19 23:27                 ` Ciaran McCreesh
2009-09-19 22:43           ` Ulrich Mueller
2009-09-19 22:54             ` Ciaran McCreesh
2009-09-19 23:07               ` Patrick Lauer
2009-09-19 23:16                 ` Ciaran McCreesh
2009-09-19 22:48           ` Patrick Lauer
2009-09-19 23:03             ` Ciaran McCreesh
2009-09-19 23:26               ` Patrick Lauer
2009-09-19 23:35                 ` Ciaran McCreesh
2009-09-20  0:37                   ` Patrick Lauer
2009-09-20  0:44                     ` 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=20090919233849.1d7713f3@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-pms@lists.gentoo.org \
    --cc=patrick@gentoo.org \
    --cc=trelane@trelane.net \
    --cc=ulm@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