1 |
On Sun, Mar 31, 2013 at 12:59 AM, Mike Frysinger <vapier@g.o> wrote: |
2 |
> the new texinfo-5.x series has rewritten makeinfo in perl. the main `info` |
3 |
> program is still in pure C. |
4 |
> |
5 |
> when it comes to packages installing .info pages, it's largely limited to the |
6 |
> GNU projects as the format has never really caught on. many of those projects |
7 |
> also install man pages. |
8 |
> |
9 |
> personally, i've never found info pages usable. for most utils, the man pages |
10 |
> or the --help output is sufficient, and for people doing heavy development, the |
11 |
> online html manuals are significantly more useful. |
12 |
|
13 |
agreed. |
14 |
|
15 |
> |
16 |
> when it was pure C, i could live with it as it's only <1MiB and no real deps |
17 |
> to speak of. now it's more like 3MiB, and pulls in 3 semi-uncommon additional |
18 |
> perl packages (not to mention perl itself). |
19 |
> |
20 |
> it's in @system for two reasons: it provides `info` and `makeinfo`. the |
21 |
> former is for reading info pages (i.e. RDEPEND) while the latter is used for |
22 |
> generating info pages (i.e. DEPEND) when the tarball didn't ship with them |
23 |
> pregenerated (they usually do). |
24 |
> |
25 |
> one option would be to make the makeinfo stuff into a USE flag so all the perl |
26 |
> junk isn't pulled in by default. only the packages that actually generate |
27 |
> info pages can DEPEND on that. |
28 |
> |
29 |
> it'd be simpler if we just dropped it altogether from @system. if people want |
30 |
> `info`, they can `emerge` it themselves. if packages want `makeinfo`, they |
31 |
> can DEPEND on it -- few fall into this category (<100 by a rough survey of |
32 |
> random Gentoo installs). |
33 |
> |
34 |
> obviously my preference is for the latter. |
35 |
> -mike |
36 |
|
37 |
I agree with the later as well. |
38 |
|
39 |
-- |
40 |
Doug Goldstein |