| 1 |
On 12 May 2014 21:35, Tom Wijsman <TomWij@g.o> wrote: |
| 2 |
|
| 3 |
> What about putting multiple doc / man / info files in a single .xz file |
| 4 |
> for each package? |
| 5 |
> |
| 6 |
|
| 7 |
|
| 8 |
How would one use them if they're installed as a single .xz file per |
| 9 |
package? |
| 10 |
|
| 11 |
Is there a trick that exists to allow this to even work for "man man" ? |
| 12 |
|
| 13 |
I'm guessing you *could* have an extension wrapper that handles a symlink |
| 14 |
to such a file to extract the desired content, but that seems messy. |
| 15 |
|
| 16 |
( ie: less /path/to/bar.polyxz => polyxz /path/to/bar.polyxz => polyxz |
| 17 |
reads symlink target, decodes the .xz file and returns "bar" from it based |
| 18 |
on the symlink source name ) |
| 19 |
|
| 20 |
Though I'd imagine that would mitigate the marginal savings made by |
| 21 |
unifying them as a single file by needing extra file system allocations to |
| 22 |
house the symlinks. |
| 23 |
|
| 24 |
-- |
| 25 |
Kent |
Archives