[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: roundcube

On Tue, 2007-02-13 at 13:22 +0100, Vincent Bernat wrote:
> On Tue, 13 Feb 2007 00:42:22 -0800, Richard Laager <rlaager@wiktel.com> wrote:
> > On Mon, 2007-02-12 at 21:19 +0100, Vincent Bernat wrote:
> >> OoO En cette  matinée pluvieuse du lundi 12  février 2007, vers 10:11,
> >> sean finney <seanius@debian.org> disait:
> >> 
> > 
> > Do these files really need to stick around for 15 days?
> I don't think. But it is a safe value.

Sure, but can we get something smaller that's still safe? On a busy
server, 15 days might be too long. I realize it's customizable, but I
think we should be able to find a reasonable default.

> >> RoundCube  can be localized.  However, the  localization files  are in
> >> separate  tarballs. Should  I  package them  as  separate packages  or
> >> should I include the translation into the main package ?
> > 
> > Are those tarballs released separately from Roundcube?
> Yes.

I was really asking if they were released at different times (mainly
more or less frequently) or with different version numbers. It seems
they're not.

Feedback from a DD would be helpful here. There are 24 language packs,
by my count. I'm inclined to say that they should be separate binary
packages, at least, since people won't necessarily want every single
language installed. (When I install RoundCube for my employer, we
probably won't want all the languages, for example.) From there, the
question is if you want to make them separate source packages as well.
That seems klunky to me, but so does repacking the .orig tarball.

Personally, I think repacking the tarball would be the lesser of two
evils. I'd unpack all the language tarballs into some subdirectory,
creating something like this (using two random language tarballs that I
looked at as examples):


Then in your debian/rules, you could do something like this:

for language in localization/* ; do
	cp -R $language/*/ debian/roundcube-`basename $language`/path/to/install/localization/

This is really rough code and completely untested, but it should give
you the idea.

In debian/control, you'd have multiple binary packages listed, of the
form roundcube-LANGUAGE.

In this way, adding a new language is as simple as unpacking a new
tarball and copying/pasting/modifying the appropriate new snippet in

Again, I'm not a DD, so if someone who is wants to chime in, take their
advice over mine. ;)


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: