Klaus Singvogel <kssingvo@suse.de> writes:
Andreas Jaeger wrote: [...]
For languages we discussed previously already the following and will implement this now: The idea is to add to spec file of packages a new rpm macro so that subpackages are created and then related subpackages are repacked for each language in our build system. This way we would get e.g. basesystem-$lang and gnome-$lang packages and those can then be installed.
So, am I right? We want to split every package and every subpackage in language differented packages? We want that result: package-$lang, package-sub1-$lang, package-sub2-$lang, ...
Is it goal to split single language files into language subpackages, e.g. a manual page? If not, is it goal to split two language files into language dependend subpackages? etc. :-) What should become the golden rule here?
This would be done via rpm magic, no need to do it yourself (like debuginfo today). Autobuild would then merge the different subpackages into a bigger one.
Wouldn't that remove a lot of the clearness in the package system?
This is currently under investigation by some developers.
Wouldn't that result in lot of fragmenation of the installation media?
No, it wouldn't.
I might want to consider here, that it was a challenge of not having enough space on the installation media in the past, and we had only a selecting of right packages for the single installation media. Doing this additional fragmentation might advance it again.
Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126