Forum .LRN Q&A: Re: Catalog files update ?

2: Re: Catalog files update ? (response to 1)
Posted by Peter Marklund on
Malte, here is a partial answer:

1) We are working on a new upgrade/merge support mechanism for catalog files that will make committing catalog files from the translation server to CVS easier and less error prone. The new approach means we are doing the merging in OpenACS rather than relying on CVS to do it for us. If there are merge conflicts then manual inspection would probably still be required before we can commit the files to CVS. Also, I'm not sure I'd be comfortable committing a whole bunch of files to CVS without manual inspection.

3) It would certainly be fairly easy to generate tarballs with catalog files from the translation server. If you want to work on this feature, Malte, feel free. I can point you to the procs to use.

Thanks for the feedback!

3: Re: Catalog files update ? (response to 2)
Posted by Malte Sussdorff on
Okay, I'll do #3 ;). Here is my thinking:
  1. Create a scheduled proc that updates the catalog files out of the database nightly. Something like db_foreach package_key { and here I need your help or look it up in acs-lang }. Files should be stored in a seperate directory structure for each locale (e.g. /tmp/de_DE/packages/...)
  2. Create a bash-script, that tar's up the up to date catalog files and stores them somewhere to download (e.g. /www/catalog/de_DE.tgz)
  3. Write a documentation for new users on how to download the catalog file.
Obviously Peter would have to install it at one stage on the translation server as I doubt it would make much sense if I provide this on my laptop.
4: Re: Catalog files update ? (response to 3)
Posted by Joel Aufrecht on
We have a mechanism for installing packages from a central repository - go to and then and you will see a link that is broken, but Lars will fix it as an alpha requirement.  It does direct d/l and install from an repository.  I think we should use this mechanism for installing new languages or updating languages, but I'm not sure how that integrates with synchronizing new work.