On 10/09/2012 08:39 PM, David Malcolm wrote:
On Tue, 2012-10-09 at 20:20 +0300, Panu Matilainen wrote:
On 10/09/2012 08:15 PM, Lennart Poettering wrote:
On Tue, 09.10.12 10:54, Seth Vidal (skvidal@xxxxxxxxxxxxxxxxx) wrote:
On Tue, 9 Oct 2012, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 10:18:27AM -0400, Seth Vidal wrote:
You'll need to get the packaging team on board with it. I have to
say it is pretty much non-existent as a priority to anyone I've
spoken with.
If we can save space in the minimal cloud image, it seems worth doing to me.
Looks like in the current EC2 instance, it's about 35M (minus a few K for
licenses).
35M? That feels a lot like 'meh' to me.
It's 28M of my 434M F18 container image. i.e. 6.5% of the disk space.
/usr/lib/locale and /usr/share/locale are 148M of my 434M container
image, i.e. 35%. I wonder if we could do something about that. Is there
a way to tell yum not to install any translations, or just translations
for a certain set of languages?
Yup, another rpm macro configuration item (this is obviously the default):
# A colon separated list of desired locales to be installed;
# "all" means install all locale specific files.
#
%_install_langs all
Is this something that Anaconda could change, based on the language
settings provided by the user in the UI? How well do rpm and yum work
if you actually change this config?
Anaconda used to support this, maybe up to RHEL-4 era or thereabouts.
Both rpm and yum work fine with this as such, presto might have to
revert back to downloading full packages (but I'm not sure about that)
The big problem with selective locale installation is that it's a
one-way street: there's no way to install new locales short of fully
reinstalling all affected packages (or the entire system, while at it).
So while it might be fine for special-purpose installations / images,
it's not that useful on a general purpose installation.
- Panu -
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
