From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-doc/eclass-manpages/files/
Date: Tue, 26 Mar 2019 15:52:28 -0400 [thread overview]
Message-ID: <d6e4e80a-30c4-0cd3-1704-ed44bba032a8@gentoo.org> (raw)
In-Reply-To: <41b890bf2dc6081badf9f4939eeb201d87ff8dac.camel@gentoo.org>
On 3/26/19 3:43 PM, Michał Górny wrote:
> On Tue, 2019-03-26 at 19:33 +0000, Aaron Bauman wrote:
>> commit: 2e32186bbee30a4a2e1c4f37c79c61897e53d8df
>> Author: Michael Mair-Keimberger <m.mairkeimberger <AT> gmail <DOT> com>
>> AuthorDate: Tue Mar 26 19:28:48 2019 +0000
>> Commit: Aaron Bauman <bman <AT> gentoo <DOT> org>
>> CommitDate: Tue Mar 26 19:32:52 2019 +0000
>> URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e32186b
>>
>> app-doc/eclass-manpages: remove unused file
>>
>
> Cool. It figures life's gonna be much easier now that we don't have
> the tool to generate those manpages.
>
In their defense, that package is structured ridiculously. We certainly
shouldn't be using $FILESDIR as the source control repository for the
shell/awk scripts that generate the man pages. If anything, they belong
in their own package, with their own "upstream" project/repository. The
eclass-manpages package would then (build-) depend on the scripts -- at
least for -9999 version that builds them on the fly.
next prev parent reply other threads:[~2019-03-26 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1553628772.2e32186bbee30a4a2e1c4f37c79c61897e53d8df.bman@gentoo>
2019-03-26 19:43 ` [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-doc/eclass-manpages/files/ Michał Górny
2019-03-26 19:52 ` Michael Orlitzky [this message]
2019-03-26 20:04 ` Michał Górny
2019-03-26 20:09 ` Aaron Bauman
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=d6e4e80a-30c4-0cd3-1704-ed44bba032a8@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-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