Poking around in OOo installation sets (as a preparatory work on
rethinking the packaging process---more on this to come), I have a few
questions. (Most of my poking took place in a standard SRC680m202
unxlngi6.pro OOo rpm installation set as built by Sun Hamburg.)
- Are ./LICENSE, ./LICENSE.html, ./README, ./README.html,
./THIRDPARTYLICENSEREADME.html (all from package -core02-) always in en-US?
- Why is ./LICENSE also available as ./LICENSE.html, ./README also
available as ./README.html, and ./THIRDPARTYLICENSEREADME.html not also
available as as ./THIRDPARTYLICENSEREADME?
- Why are ./LICENSE and ./LICENSE.html doubled as
./licenses/LICENSE_en-US and ./license/LICENSE_en-US.html (also package
-core02-), and ./README and ./README.html doubled as
./readmes/README_en-US and ./readmes/README_en-US.html (also package
-core02-), but not ./THIRDPARTYLICENSEREADME.html?
- Why are all the (localized, plain and html) license and readme files
at ./licenses and ./readmes doubled at /share/readme? (All en-US ones
are from package -core02-, all localized ones are from respective
-<LOCALE>- packages.)
- The ./program/resource/*680en-US.res files are split across -base-,
-calc-, -core08-, and -math-, while the corresponding files for any
other locale are bundled in -<LOCALE>-res-. Why are the en-US files
split across packages, and why is -core08- (the package that contains
most of them, and exclusively such res files) not called -en_US-res-
instead?
- Why is ./program/unopkg_gui (a trivial shell script to execute "unopkg
gui") part of (various different) desktop integrations (e.g.,
-mandrivia-menus-, -redhat-menus-, -suse-menus-) and not just once and
for all put into the same package as ./program/unopkg itself (-core02-)?
- What are the ./share/xdg/*.desktop files (from various packages) used for?
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
