Gentoo Archives: gentoo-dev

From: Michael Orlitzky <mjo@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-doc/eclass-manpages/files/
Date: Tue, 26 Mar 2019 19:52:39
Message-Id: d6e4e80a-30c4-0cd3-1704-ed44bba032a8@gentoo.org
In Reply to: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-doc/eclass-manpages/files/ by "Michał Górny"
1 On 3/26/19 3:43 PM, Michał Górny wrote:
2 > On Tue, 2019-03-26 at 19:33 +0000, Aaron Bauman wrote:
3 >> commit: 2e32186bbee30a4a2e1c4f37c79c61897e53d8df
4 >> Author: Michael Mair-Keimberger <m.mairkeimberger <AT> gmail <DOT> com>
5 >> AuthorDate: Tue Mar 26 19:28:48 2019 +0000
6 >> Commit: Aaron Bauman <bman <AT> gentoo <DOT> org>
7 >> CommitDate: Tue Mar 26 19:32:52 2019 +0000
8 >> URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e32186b
9 >>
10 >> app-doc/eclass-manpages: remove unused file
11 >>
12 >
13 > Cool. It figures life's gonna be much easier now that we don't have
14 > the tool to generate those manpages.
15 >
16
17 In their defense, that package is structured ridiculously. We certainly
18 shouldn't be using $FILESDIR as the source control repository for the
19 shell/awk scripts that generate the man pages. If anything, they belong
20 in their own package, with their own "upstream" project/repository. The
21 eclass-manpages package would then (build-) depend on the scripts -- at
22 least for -9999 version that builds them on the fly.

Replies