Hi Osma,

> > I think I always use the --force flag, I can't remember why though.
> > Probably some updates are not performed if I omit it, likely
> > because of date stamps as you highlighted.
> 
> The flag was not in the transifex script, I had to add it manually I
> think.

Ok, I may have done a local modification :).

> My suggestion would be to move things around so that everything
> necessary
> to build the localization packages would be contained within the
> subtrees
> of the respective source packages. The sources should be served as
> normal
> Debian source package repositories.

Yes, simpler is better, I agree we should make it simpler!

> apt-get source doudoulinux-l10n
> apt-get build-dep doudoulinux-l10n
> cd doudoulinux-l10n*
> debian/rules pull-transifex # custom rule (is it allowed?)
> debian/rules binary

I like this one :).

I think we are free to create any rule in Makefiles, especially if this rule is 
independent from all the other ones, which seems to be the case. I don't know 
much of Makefiles but understood that it is designed to be very flexible. 

What would be logical, would be to host doudoulinux-l10n in "lang/" in the end, 
so that we don't need a copy of PO/TS files in "packages/" anymore. As it now 
weights around 1GB, this is an important change to consider! To say the truth, 
the tree "docs/" that is used to build the PDF documentation from our website, 
has its own Debian package code.

Concerning the schedule, version 2.2 is planned for March/April to provide 
better translations, mainly. I'm currently working on 2.5 that will *not* 
provide the ability for our contributors to work on translations (2.5 will be 
based on Wheezy, not Squeeze, but will look like the 2.x branch). I'd like to 
publish version 2.5 for the spring. Version 3.0, based on Wheezy, is not 
expected before the end of 2014. It should bring a major change of the look and 
feel as well as new applications, plus better translations. Ideally, 
intermediary versions between 2.5 and 3.0 would be published as development 
versions, to allow people test and start working on translations.

I think we can start to change "lang/" and doudoulinux-l10n for 2.5, in the SVN 
trunk. I've already started to push changes in the trunk for 2.5 indeed. And 
our Debian repository has already been populated with several Wheezy packages.

So now the most important question: do you feel the motivation to perform all 
these changes by yourself?

Cheers,
JM.

_______________________________________________
Doudoulinux-lang mailing list
[email protected]
https://mail.gna.org/listinfo/doudoulinux-lang

Reply via email to