| 1 |
On Jan 09 09:30:11, ikelos@g.o wrote: |
| 2 |
> Hiya Jan, |
| 3 |
> |
| 4 |
> The following snippet from Ingo is correct: |
| 5 |
> |
| 6 |
> > So, you want to hear something constructive? Your best option is to |
| 7 |
> > just decompress that stuff on your system. (Gentoo is famous for |
| 8 |
> > its excessive configurability - maybe there is even an option?) |
| 9 |
> |
| 10 |
> We are both famous for our excessive configurability and there is even |
| 11 |
> an option already! 5:) If you look in the manpage (once you've |
| 12 |
> decompress it somewhere, or online at [1]) for make.conf, you'll see the |
| 13 |
> entry for PORTAGE_COMPRESS, which you can set as follows: |
| 14 |
> |
| 15 |
> PORTAGE_COMPRESS="" |
| 16 |
|
| 17 |
I am only a user on this system, |
| 18 |
and have no control over which packages are installed |
| 19 |
and have no write permissions in /usr/share/man/ or make.conf |
| 20 |
|
| 21 |
> As mentioned in [2,3,others]. You'll then need to reinstall all |
| 22 |
> packages. If you manually decompress the files, then the uncompressed |
| 23 |
> manpages won't be registered with portage and won't get removed if the |
| 24 |
> owning package is uninstalled. |
| 25 |
|
| 26 |
Also, the uncompressed manpage will not get updated |
| 27 |
when the packages gets updated. I will have two copies, |
| 28 |
a stale *.1 and an up-to-date *.1.bz2. |
| 29 |
|
| 30 |
These are workarounds. Let me get back to the original question: |
| 31 |
would you please consider having _uncompressed_ manpages as the default? |
| 32 |
|
| 33 |
On this particular system, the bzipped /usr/share/man/ is 67M. |
| 34 |
The uncompressed man/ is 108M. That's 40M saved. Seriously? |
| 35 |
|
| 36 |
There is an option to support; the packages need to be reinstalled |
| 37 |
or there are untracked files; the manpage formatter needs to call |
| 38 |
external unpackers. All this to save 40M. I honestly don't think |
| 39 |
it's worth it. |
| 40 |
|
| 41 |
Jan |
Archives