[mm-deb] Re: [Pkg-mailman-hackers] Selecting language specific stuff to be installed

Siggy Brentrup bsb@debian.org
Tue, 23 Mar 2004 22:30:43 +0100


--69pVuxX8awAiJ7fD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Mar 23, 2004 at 09:29:14PM +0100, Laszlo 'GCS' Boszormenyi wrote:
> Hi,
>=20
> On Thu, Mar 04, 2004 at 02:46:47PM +0100, Siggy Brentrup <bsb@debian.org>=
 wrote:

> > Most (list-)adminstrators will not want to support the full range
> > of available languages on their system; I guess between 1 and 3
> > languages will be most common.
>  Sorry for my very slow comment on this, no excuses. Well, I wonder
> how we should handle #238377 (split languages into separate package)
> now. I like your proposal (and the solution itself as well, as it's
> well designed),...=20
thanks for the roses :)

> ... and we can make a mailman-i18n or so package out of the language
> files, mailman depending on that.

I don't think this is really necessary, a better solution might be to
split mailman, mailman-common and mailman-doc with mailman depending on
mailman-common which contains among others all python code.

[...]

> > An implementation might use a debconf question like locale does or
> > even decide based on which locales are installed, the latter
> > approach with the drawback of requiring a reconfigure of mailman
> > whenever locale is reconfigured.

>  Thanks for the solution!=20
> Unfortunately the postinst became more chatty, as now (ok, only the
> first time) I get more info on what's going on for removing language
> files.

Blame ucf for the chattyness, it needs a --quiet option producing
output only when user interaction is required, I'll file a wishlist
bug.

> Also I get plus one line for adding the new localised files, probably
> because ucf --three-way.
Yes, that's the reason, but you won't see it again unless you modified
a template,

> I do not know why, but I have one file left in each language I
> haven't selected: admlogin.html; trying to look into this.
Oops, I didn't see this. From which mailman version were you upgrading?
I tested 2.4.1-1 -> 2.4.1-2 only.

btw: http://www.winnegan.de/mailman has an updated 2.1.4-1 ready for
     uploading.

Regards
=2E Siggy

--69pVuxX8awAiJ7fD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAYKyD94B/SGO8KQcRAmG4AJ48Hmted5Z01qFFi4ELsgiA8MoVaACgq3EJ
2WW/q3MC/CWORx0AFZh1T+U=
=ovxi
-----END PGP SIGNATURE-----

--69pVuxX8awAiJ7fD--