Mailinglist Archive: opensuse-translation (86 mails)

< Previous Next >
Re: [opensuse-translation] translation-update
  • From: "Ladislav Michnovič" <ladislav.michnovic@xxxxxxxxx>
  • Date: Thu, 6 Dec 2007 15:15:53 +0100
  • Message-id: <202bcdd90712060615u5ce67a43q78ca195f03673a5d@xxxxxxxxxxxxxx>
2007/12/6, Carlos E. R. <robin.listas@xxxxxxxxxxxxxx>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



The Thursday 2007-12-06 at 10:46 +0100, Karl Eichwalder wrote:

For LCN it would be harder, because the translations are distributed
in various packages.

This could be done using the overload strategy with the shadow directory
for the .mo files. We did those things for SLED10. The package name is
translation-update.

The tough part is to get rid of the package if you update from 10.3 to
11.0.

Ouch.

It has to be an optional package, with a warning to the user; and then try
to remind whoever does that in Yast development to remove the package on
upgrade... not a clean solution, it can backfire.

I have an idea how to solve it. Create this package within Suse and
do a proper numbering. For example 10.3.x.y, which shows, that it is
connected to openSUSE Linux 10.3. Release translation updates as
often as needed, but when next SuSE release comes, renumber it to
11.0.x.y and make this package empty. This package will come within
installation media and it would be without any files, only README for
some information. If somebody will do an update, YaST, zypper, rpm can
handle this and will erase all files which was installed on the system
by that package in previous version. One thing is needed, to make some
dependency on some basic package or Pattern which will ensure, that
this package will be always installed. Ask YaST2 maintainers for
details.

Regards Ladislav.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-translation+help@xxxxxxxxxxxx

< Previous Next >