Re: TDebs?

[Otavio Salvador <otavio@debian.org>]

"Aigars Mahinovs" <aigarius@gmail.com> writes:

>>  - how can I do to avoid upgrade tdebs when there's no translation
>>    changes?
>
> I have not thought of that problem before. There are three ways to solve this:
> 1. Introduce translation versions in the Translations file, status
> file field and file names of the translation packs. Then a
> Translations file is really needed.

I can identify the need of version but why we would need the file
names and status file?

When installing a package we might build the tdeb and use the md5sum
of content files as version "number" so it would detect if it needs
upgrade or not. Might work.

> 2. Do some wierd magic with linking the file with the translations for
> the old version into the place where the new translation should be and
> then comparing some metadata remotely - flacky.

Uh! *DANGER*!

> 3. Do not solve it at all. It would still beat the current situation -
> currently, if there is a new package version, I need to redownload the
> transation inside the package anyway, even if the translation did not
> change, even download translations I do not care about. - simplest way

Simple... :-D

>>  - when upgrading from etch to etch+1 (let's think it'll be done
>>    there) dpkg, apt and aptitude would be need to be upgraded _before_
>>    anything else. Will be some stages where no translation will be
>>    found. Will be it be a problem for dpkg?
>
> If we implement this for etch+1 and a user upgrades by first
> installing new dpkg and apt, then he would have no translations for
> dpkg and apt at that point. If he just does a dist-upgrade, he would
> have no translations at all until he configures the languages he needs
> and runs the new apt. That would have to go into the release notes
> then.

Or better. The apt might use an external tool to "install"  the tdebs
and it be called at end of apt runs and check for pending and need
translations. That would make the upgrade simple while we lose the
translation while in process.

>>  - Do a libc change be need?
>
> Not required if we allow tdebs to overwrite files of the base packages.

I prefer to change libc to avoid overwrite files. But it's my POV.

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."