[perldoc2-developers] Pootle, was datase vs. versioning

[Joergen W. L. <joe...@gm...>]

Nicolas François schrieb:
> On Tue, Dec 12, 2006 at 10:59:19AM +0100, Robert 'phaylon' Sedlacek wrote:
>> Hi Joergen,
>>
>> Joergen W. Lang wrote:
>>
>>> Pootle appeared to promising but didn't want to install on my 
>>> Debian/Sarge machine without a kernel change or a lot of manual 
>>> instllation. Or does it make more sense to just use that? I'm still not 
>>> 100% sure.
>> What did it need _that_ for?
> 
> It is "just" a dependency issue.

Exactly.

> The python modules packaging changed between Sarge and the current
> Debian release, so pootle requires a new python infrastructure, which
> probably requires the new libc, etc.

Also, Python 2.5 did not like to install from source. Since the Debian 
machine is my production server I do not like to mess around with it too 
much. I can try to run it on my local machine (Mac OS X) but that would 
only give us *very* limited access since I share the DSL line with three 
other parties.

I will meet with a Python expert tonight. Maybe he can shed some light 
on the situation.

So, if we wanted to use Pootle as the platform we are left with three 
options:

1. Get perldoc 2.0 onto the "official" wordforge/Pootle server
2. Find some other webspace provider with the neccessary infrastructure
3. Build our own from scratch

(your ideas here)

> Pootle can be installed on its own (it requires jToolkit, which requires
> kid and elementtree).

Downloaded these. Will give it another try later today.

> Regarding the infrastructure, except if we want to have mass translation
>>from a web interface, the subversion interface + commit logs for reviews
> + export on a web interface is perfect for me.

Hmmm, maybe a compromise will suffice. Use Pootle as long as we have to 
and later migrate to our own platform.

I will contact the Pootles by mail and see what they have to say about it.

Greetings,

Joergen