I couldn't believe it too, but it's the .po files that make it that big.
There are only three little SRPMS in the tarball.
David
We can ask for an increase on google code for space. They are most
often, more than happy to increase your space you can have.
David
Ramboz Pierre-Henri napsal(a):
> its my 'pro' server
> the one i use for my client.
> i only use 5% of its power for the other project i host
> yet santarepo is hosted there !
> so no worries about life uncertainity ... it will be sufficient for the
> work we plan we designed !
>
> 2008/10/14 Alessio Adamo <alessi...@gmail.com
> <mailto:alessi...@gmail.com>>
>
> I subscribe to didouph's concern about launchpad. I hope that google
> code will accord us some more room, because I think that for public
> and shared projects a public server is always preferable than a
> private one (did I misunderstood that that is your own server?).
> Google code should be safer and easier to manage and less dependent
> on "life uncertainties".
>
> Anyway I'm happy to hear this news. Apparently many flies are
> buzzing around this dead project. ;-)
>
>
> 2008/10/14 Ramboz Pierre-Henri <did...@gmail.com
> <mailto:did...@gmail.com>>
>
> you came pretty close to the curent status of my research.
>
> with the help of david, we have a svn repo over ssh (secured
> like hell) with virtual user who can read and write on the server.
> at the very moment the setup require a per user rsa keypair to
> authenticate ... so every single person would have to provide a
> rsa pubkey to be allowed to read from our svn
>
> to byspass that i'm thinking of 3 solutions :
> 1 : svn web interface (read only)
> 2 : preshared pub key among several users to allow loggin to svn
> over ssh (read only)
> 3 : release bundle (tar.gz svn snapshots built on a dayly/weekly
> basis)
>
> I really think that launchpad is a "masochist" tool but if you
> all like it, it could be used as a front end to svn if it
> supports svn over ssh and also as a host for release files. we
> also could meve both wiki and discussions to launchpad but it
> would be painfull to reach users.
>
> So we almost have dealt with the technical issues and at least
> have something functional and big enough to host the project
> If we all are for launcpad, lets do it but don't cry if you just
> don't understand how it works (since it's much more complex than
> svn imo)
> But what about the community? away from both pclinuxos.com
> <http://pclinuxos.com> and mypclinuxos ... if we go launchpad
> ... we would be very far from pclinuxos user sphere ! ... how to
> keep the connection active ? how to stay in touch with the gang
> if we are not even on the same domains ?
>
> DidouPh
>
> 2008/10/14 Zoltan Hoppar <hop...@gmail.com
> <mailto:hop...@gmail.com>>
>
> I think here is the solution for everyone. For the devel
> team (the ripper gang) will get the svn+shh server, sync
> and simple fast secured access. For public tracking it would
> be nice for the new coming people to get their base pot,
> sample files, srpms, testing files, docs, backuped snapshot
> (like gianvacca's zipped file) etc - and a good base for
> begun translation for pclos. For more closer tracking, with
> teams, with simplier frontend for the masses, who wants to
> translate in their team, the solution is launchpad. If we
> could manage this to get connected, sync'ed time to time -
> then we get an safe and secured devel side, and an easy to
> use "average-joe" translator frontend on the other side. If
> this works, then berlios - maybe we don't need it at all.
>
> Zoltan
>
> 2008/10/14 Ramboz Pierre-Henri <did...@gmail.com
> <mailto:did...@gmail.com>>
> <mailto:did...@gmail.com>>
>
> don't worry ... it wasn't such an alarm, just a
> critical matter that arose back from your post!
>
> we have not yet picked a good host for our code!
>
> lets just keep playing with it for a wile
> i'm looking forward to increase space
>
> code-h...@google.com
> <mailto:code-h...@google.com> sounds to be the
> place to ask
>
> and there is something comming out my server that
> could help if i don't get blacklisted on it !!
>
>
> didouph
>
> don't worry ... we will find a place !
>
> 2008/10/13 Alessio Adamo <alessi...@gmail.com
> <mailto:alessi...@gmail.com>>
>
> Just to add that only yesterday did I discovere
> that more than 100 MB are required. It occurred
> when my attempt to upload all the po files to
> google svn failed after 20 min, saying that I
> had exceeded the disk quota.
> When I calculated the size of the folder I
> couldn't believe it, but I checked for "ghost
> files" and I couldn't find any. Even after
> cutting some branches no way I could bring it
> below 100 MB.
>
> As I said, I've uploaded there just for sharing
> it, and discuss about what to do, what our moves
> should be.
>
> If asking for additional room on google code is
> not a problem, we can do so, my vote goes for
> it. Otherwise we stay in berlios and that's it.
>
> Once this important detail has been sorted out,
> we should also discuss what shape to give to the
> SVN/CVS tree, how to organize that awful lot of
> files.
>
> 2008/10/13 devnet <dev...@gmail.com
> <mailto:dev...@gmail.com>>
>
>
> On Mon, Oct 13, 2008 at 2:51 AM, Ramboz
> Pierre-Henri <did...@gmail.com
I'll add your translations to our SVN and to Pootle (l10n.ipclinuxos.com).
I can't promise you these translations will appear on PCLOS 2009 liveCD though.
From now on please use our new online translation portal l10n.ipclinuxos.com to
add/edit translations.
Team members contact list is a good idea and I think we'll definitely put it
somewhere. Anyway the new guy you're talking about should join this mailing list
first.
David
I wasn't aware of that, thanks for the report.
All that was needed was a little fix in translate toolkit source code.
> BTW. Some languages do not have all the po files to translate through
> pootle and pclinuxos-messages.pot is not the real template of the po
> files we have.
I'm adding those po files as soon as I see somebody speaking that language has
registered. It's possible to do using the web interface.
David
All the .po files in SVN and Pootle are taken from testing repository, so they
should be as near to PCLOS 2009 as possible.
Don't worry about translating all over again, in case of an upstream change in
.pot we'll take care of updating all the .po files, only completely new messages
or changed messages will have to be translated then.
What should I do with the .po files you've sent ? Do you want me to merge it
with current translations in Pootle (and SVN) ?
David
The menu-messages.pot was a real mess (originating from upstream SRPM).
I've corrected it and made it contain all msgids that are used in .po files and
I also updated all .po files in Pootle to correspond with this new .pot.
David
Slaviša, your .po files have been merge into Pootle. You can translate freely now.
David
There already are some Croatian translations, they just were not
activated/visible in Pootle. I did not copy anything because some translations
seem to be more advanced than sr@Latn.
You now have privileges to translate Croatian .po files, so please use the
upload/merge feature to copy sr@Latn .po files over the Croatian ones where
appropriate.
David