| 1 |
On Thu, 19 Feb 2009 12:06:17 +0100 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
> Package managers supporting compression would internally maintain two |
| 4 |
> lists of paths, both having a default value, plus the possibility to |
| 5 |
> modify them from ebuilds/eclasses: |
| 6 |
> |
| 7 |
> - an inclusion list, initially containing: |
| 8 |
> /usr/share/doc /usr/share/info /usr/share/man |
| 9 |
> - an exclusion list, initially containing: |
| 10 |
> /usr/share/doc/${PF}/html |
| 11 |
> |
| 12 |
> Then we need a new command, let's call it "docompress" for now (name |
| 13 |
> to be discussed), to manipulate the lists: |
| 14 |
> |
| 15 |
> - "docompress" (without option or with option "-a"): add paths |
| 16 |
> (directories or files) to the inclusion list |
| 17 |
> - "docompress -d": delete paths from the inclusion list |
| 18 |
> - "docompress -x": add paths to the exclusion list |
| 19 |
> - "docompress -x -d": remove paths from the exclusion list |
| 20 |
> (maybe this is not needed?) |
| 21 |
|
| 22 |
If there's an inclusion list and an exclusion list, there's only a need |
| 23 |
to delete things from the exclusion list if the exclusion list has bad |
| 24 |
initial values, and never any need to delete things from the inclusion |
| 25 |
list. And since reliably rewriting links in HTML when compressing is at |
| 26 |
best tricky and at worst impossible (think JavaScript navigationy |
| 27 |
things), is there ever going to be any need for removing from the |
| 28 |
exclusion list? |
| 29 |
-- |
| 30 |
Ciaran McCreesh |
Archives