File translation-update-upstream-HOWTO of Package translation-update-upstream

Overview Repositories Revisions Requests Users Attributes Meta

File translation-update-upstream-HOWTO of Package translation-update-upstream (Revision 9227ed75c2f35659043046a8db48aadd)

Currently displaying revision 9227ed75c2f35659043046a8db48aadd , Show latest

If you want to add translation-update-upstream support to a package
===================================================================

1) Add to preamble:

BuildRequires: translation-update-upstream

2) Immediately after %setup (and before possible
gnome-patch-translation-prepare) add command:

translation-update-upstream

3) Add configuration for this package to translation-update-upstream and
update translations.

If you want to update or add single translation
===============================================

Add a line to a proper configuration file (or create a new one -
anything with nale *.tlst is sourced automatically).

If your project uses a non-standard directory or SVN hierrarchy, you may
need a code into a *.hook file.

Then run following command in unpacked sources directory:

./upstream-collect.sh {package_name}

where {package_name} is the name of the package you need to update.

Then you have to edit spec file to include new tarball, rebuild it and
rebuild the package using the new version of translation-update-upstream.

Note that the shapshot date of the package will not be updated, but
instead of it, a sub-version will be used.

You need osc, network connection, cvs, svn, all commands needed to run
%prep of packages (e. g. patch or gnome-patch-translation) and network
connection.

If you want to update translations (short process: update translations only)
============================================================================

Run following command in unpacked sources directory:

./upstream-collect.sh

It creates a tarball with translations updated by upstream using all
existing *.tlst filůes (configuration of packages) and
upstream-collect.conf (configuration of tool itself).

Then you have to edit spec file to include new tarball, rebuild it and
rebuild all packages using new version of translation-update-upstream.

You need osc, network connection, cvs, svn, all commands needed to run
%prep of packages (e. g. patch or gnome-patch-translation), network
connection and lot of time.

If you want to update translations (long process: update configuration)
============================================================================

Just now the file upstream-collect.lst is automatically generated by
lower mentioned tools.

You need a complete binary RPM repository available on a filesystem and
refer to it in create-config.conf

Then you can run following command in unpacked sources directory:

# collect possible po domains from rpm packages
./create-tlst-step1-list-all-po-projects.sh
# scan upstream branches
./create-tlst-step2-create-gnome_svn.sh

Then continue as above.

Places

File translation-update-upstream-HOWTO of Package translation-update-upstream (Revision 9227ed75c2f35659043046a8db48aadd)

Places