From: Pacho Ramos <pacho@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: deprecate /usr/share/doc/$PF
Date: Mon, 19 Dec 2011 11:47:48 +0100 [thread overview]
Message-ID: <1324291668.3529.4.camel@belkin4> (raw)
In-Reply-To: <20111219093104.3cdad034@pomiocik.lan>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
El lun, 19-12-2011 a las 09:31 +0100, Michał Górny escribió:
> On Mon, 19 Dec 2011 00:07:45 +0100
> Pacho Ramos <pacho@gentoo.org> wrote:
>
> > El dom, 18-12-2011 a las 23:02 +0100, Michał Górny escribió:
> > [...]
> > > > Q6: Why can't the dodoc/dohtml path be changed before EAPI-5?
> > > > A6: Because the path where dodoc and dohtml install files is part
> > > > of the PMS. Portage can't just change it on its own. A possible
> > > > workaround for current EAPIs is adding new-style dodoc/dohtml
> > > > analogues to an eclass.
> > >
> > > I think some of devs agree we should be allowed to fix past mistakes
> > > without waiting another 20 years till the tree is migrated to a new
> > > EAPI...
> > >
> >
> > Maybe this situation could be improved if there was a policy forcing
> > us to try to use latest EAPI when possible for any package update,
> > that way we would move faster to latest eapi and even deprecate older
> > eapis easily
>
> Still unlikely. A bunch of old eclasses will force ebuilds to be EAPI 0
> or so.
>
Well, I was meaning eapis different than 0, I know it will need to be
kept more time due backwards compatibility ;)
Regarding other eapis, how many eclasses are still requiring old eapis?
I think games.eclass was one of them, but haven't reviewed others :S
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-19 10:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 21:49 [gentoo-dev] RFC: deprecate /usr/share/doc/$PF Alexandre Rostovtsev
2011-12-18 22:02 ` Michał Górny
2011-12-18 23:07 ` Pacho Ramos
2011-12-19 8:31 ` Michał Górny
2011-12-19 10:47 ` Pacho Ramos [this message]
2011-12-19 2:26 ` Alexandre Rostovtsev
2011-12-19 2:41 ` Jeroen Roovers
2011-12-19 5:31 ` Alexandre Rostovtsev
2011-12-19 11:48 ` Jeroen Roovers
2011-12-18 22:07 ` Chí-Thanh Christopher Nguyễn
2011-12-19 0:56 ` Alexandre Rostovtsev
2011-12-19 0:08 ` Ulrich Mueller
2011-12-19 1:52 ` Alexandre Rostovtsev
2011-12-19 4:23 ` Ulrich Mueller
2011-12-19 4:48 ` Dale
2011-12-19 13:29 ` [gentoo-dev] " Duncan
2011-12-19 6:41 ` [gentoo-dev] " Alexandre Rostovtsev
2011-12-19 8:23 ` Ulrich Mueller
2011-12-19 13:51 ` [gentoo-dev] " Duncan
2011-12-19 9:02 ` [gentoo-dev] " Michał Górny
2011-12-19 9:03 ` Ciaran McCreesh
2011-12-19 8:35 ` Michał Górny
2011-12-19 10:08 ` Stelian Ionescu
2011-12-21 1:44 ` Maciej Mrozowski
2011-12-21 3:40 ` Mike Frysinger
2011-12-27 17:29 ` Maciej Mrozowski
2012-01-18 11:12 ` Mike Frysinger
2011-12-27 17:39 ` Andreas K. Huettel
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=1324291668.3529.4.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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