From: Torsten Veller <tove@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] prepalldocs (was: Council log and summary for meeting on 02/12/09)
Date: Fri, 13 Feb 2009 12:55:01 +0100 [thread overview]
Message-ID: <20090213124130.TAfe8a6.tv@veller.net> (raw)
In-Reply-To: <20090212214925.GA21532@dodo.hsd1.nj.comcast.net>
* Thomas Anderson <gentoofan23@gentoo.org>:
> Technical Issues:
> - Prepalldocs
> Should the 'prepalldocs' be allowed in current EAPIs?
>
> Conclusion:
> Prepalldocs is banned in current EAPIs(0,1,2). It should be
> removed from ebuilds. Petteri Räty(Betelgeuse) will make QA
> checks for repoman.
You only did half of your job.
Do we want some docs being compressed, others not?
Do we want to have compressed docs at all?
What do you expect from maintainers now?
To me it means: Instead of using prepalldocs I will move the docdir to
a temporary place and dodoc every file back to docdir. Insane.
Maybe I add a function named prepalldocs to the ebuilds that does the job.
Thanks.
next prev parent reply other threads:[~2009-02-13 11:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 21:49 [gentoo-council] Council log and summary for meeting on 02/12/09 Thomas Anderson
2009-02-12 21:55 ` Thomas Anderson
2009-02-13 6:42 ` Tiziano Müller
2009-02-13 6:53 ` Donnie Berkholz
2009-02-13 12:08 ` Petteri Räty
2009-02-13 15:44 ` Donnie Berkholz
2009-02-13 18:06 ` Petteri Räty
2009-02-13 6:55 ` Luca Barbato
2009-02-13 11:55 ` Torsten Veller [this message]
2009-02-13 12:11 ` [gentoo-council] prepalldocs Petteri Räty
2009-02-13 13:40 ` [gentoo-council] prepalldocs Torsten Veller
2009-02-13 13:51 ` Thomas Anderson
2009-02-13 14:54 ` Petteri Räty
2009-02-13 15:54 ` [gentoo-council] Council log and summary for meeting on 02/12/09 Thomas Anderson
2009-02-13 17:20 ` Luca Barbato
2009-02-13 17:27 ` Ciaran McCreesh
2009-02-13 19:33 ` Luca Barbato
2009-02-13 19:41 ` 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=20090213124130.TAfe8a6.tv@veller.net \
--to=tove@gentoo.org \
--cc=gentoo-council@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