From: "Michał Górny" <mgorny@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Call for agenda items - Council meeting 2014-09-09
Date: Sat, 30 Aug 2014 18:07:17 +0200 [thread overview]
Message-ID: <20140830180717.06a66117@pomiot.lan> (raw)
In-Reply-To: <21505.51605.567727.858150@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Dnia 2014-08-30, o godz. 14:54:45
Ulrich Mueller <ulm@gentoo.org> napisał(a):
> I've got an item for the agenda myself:
>
> mgorny started a thread about the future of dohtml on gentoo-dev [1].
> Nobody has spoken up in favour of keeping the function.
>
> So, I am asking the council to discuss and vote on the following
> questions:
> - Should dohtml be banned from the package manager?
> - If yes, what would be the time frame? We could ban it in EAPI 6
> already. Alternatively, we could deprecate it now and ban it in some
> later EAPI.
> - Do we need a substitute in an eclass? (Note that dohtml in Portage
> is written in Python, so it would have to be rewritten from
> scratch.)
> - If the answer to the first question is no: Should einstalldirs in
> EAPI 6 use dodoc -r for HTML_DOCS, instead of dohtml?
We should also decide how to prepare developers for the change. I think
we could enable warnings for skipped files in earlier EAPIs -- if EAPI
6 will not provide any direct replacement for dohtml, developers may
already start replacing it with dodoc.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
prev parent reply other threads:[~2014-08-30 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 20:53 [gentoo-project] Call for agenda items - Council meeting 2014-09-09 Ulrich Mueller
2014-08-30 12:54 ` [gentoo-project] " Ulrich Mueller
2014-08-30 13:13 ` Ulrich Mueller
2014-08-30 16:07 ` Michał Górny [this message]
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=20140830180717.06a66117@pomiot.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--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