| 1 |
Ferris McCormick wrote: |
| 2 |
|
| 3 |
>> I |
| 4 |
>> would also like to have them excluded from binary packages. |
| 5 |
>> |
| 6 |
> |
| 7 |
> That can't be right can it? You mean, like openoffice-bin, or like the |
| 8 |
> ones you build yourself? I know that I often build on one system, install |
| 9 |
> on several, and when I do that, I really want them to be identical. I |
| 10 |
> think if you have your no-docs-of-any-kind option, you get your wish as to |
| 11 |
> locally built packages, but if you really mean things like openoffice-bin, |
| 12 |
> I doubt that any openoffice user would want it with absolutely no |
| 13 |
> documentation. |
| 14 |
|
| 15 |
Yes, if I say -doc or specify FEATURES="nodoc", I don't want the docs in |
| 16 |
there, binary package or not. I want the behavior and results to be |
| 17 |
consistent. I am not talking about things like the internal openoffice |
| 18 |
help documentation, I am talking about anything that goes |
| 19 |
into /usr/share/doc, man pages, and info pages. |
| 20 |
|
| 21 |
At my job we aim to eventually rid ourselves completely of MS products on |
| 22 |
several thousand (local and remote) desktops and replace them with some |
| 23 |
sort of thin linux client running the citrix metaframe client. They will |
| 24 |
be running in kiosk mode. No user will have the ability to get to a window |
| 25 |
manager and browse around in /usr/share/doc. They don't even know what the |
| 26 |
heck a man page is. |
| 27 |
|
| 28 |
Generating package CDs to install the kiosks, using livecds in some cases, |
| 29 |
and in other cases using terminal servers are all options on the table. In |
| 30 |
each of these scenarios, every KB counts. |
| 31 |
|
| 32 |
I also generate installation CDs that can install or update any server type |
| 33 |
in our farm for disaster recovery purposes. Again, every KB counts... |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives