Re: TDebs?

["Eddy Petrişor" <eddy.petrisor@gmail.com>]

An update...

On 28/09/06, Eddy Petrişor <eddy.petrisor@gmail.com> wrote:
> > The most difficult part, looks to be, to build an update to
> > translation. To it, we would need to have an extra mode to rules to
> > allow us to build only the translation (as we have build-arch and
> > build-indep today), e.g build-trans...

> Now, the tricky part, translation updates. The idea is to have a
> separated source package which is generated from the original source
> package which will generate the binary tdeb packages which have the
> same name as the ones in the original source. These tdeb source
> packages could be either created automatically with a tool which
> should do the most best choices in most cases when creating the
> package, or - until the need of a tool arises - by hand.
>
> Creating the source package for tdebs could prove to be tricky in
> cases where the localization info is more than simple po files or
> binaries already translated (e.g.: voices' sound tracks in games), but
> something more complicated which build during the build time of the
> package - imagine build dependencies based on which the translation
> compilation result changes, translations which are tightly bounded to
> the binary.
>
> Here is a simplified schema of the process:
>
> OSP -> all binary debs
>    |-----> a tdeb for each language for which localization material exists
>    |
>    | (after release, via a tool or manually - depends on our needs)
> TSP -> all the tdebs with bigger version number > OSP version
>
> OSP = original source package
> TSP = translation source package
>
>
> Problem: there is stil the null-improvements update problem, but which
> is not still better than the current situation. It could be argued

s/is not better/is not worse/

> that an md5 sum can be computed on the source translation material and
> confronted with the original md5-s in the previous version - but that
> should be implemented in that tool, or later.

Also, iirc, it is possible to pass to the debian/rules the binary
package which needs to be built... So, if my memory does not decive
me, uploads only for the updated tdebs could be done, without having
this issue.

> Note: Using tdebs instead of regular debs has the advantage of not
> imposing some restricted namespace, separation of localization dpkg
> information from the main information about packages.
>
> [*] e.g.: ogg files with localized messages in a game, weird
> localization information - found especially in games
> [**] yes, there willbe an explosion of packages, but those will be
> placed in different places in the archive, the /var/lib/dpkg/info
> could have a /var/lib/dpkg/info/i18n/<lang_country> directory
>
> --
> Regards,
> EddyP
> =============================================
> "Imagination is more important than knowledge" A.Einstein


--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein