[Pkg-mailman-hackers] Re: [mm-deb] RFD: How to proceed from 2.1.4-3?

[GCS]

--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline

Hi,

On Wed, Mar 31, 2004 at 01:06:05PM +0200, Siggy Brentrup <bsb@debian.org> wrote:
> - Add debconf templates for DEFAULT_{EMAIL,URL}_HOST. This will
>   possibly require major modifications to how mm_cfg.py is created,
>   I'm even considering a python postinst.
 +1, maybe automagically get it from /etc/mailname , or try to get
ServerName from the httpd.conf (in case of Apache is used) as defaults.

> - Get qmail-to-mailman.py out of /etc/mailman by modifying it along
>   the lines I use in postfix-to-mailman.py.
 Will look into this if I have some more time.

> - Split the package into mailman(arch:any), mailman-common (arch:all)
>   and mailman-doc (arch:all) and possibly mailman-i18n (arch:all) with
>   mailman depending on mailman-common.  While at it, move
>   /var/lib/mailman/messages to /usr/share/mailman, probably giving
>   each language directory there an LC_MESSAGE subdirectory.
 +1, I think it's a long awaited feature. Maybe the en, es, de (most
spoken languages) should remain in mailman, but put others into -i18n.
What's your opinion?

> - Track down the issue Joey[tm] brought to my attention, with mailman
>   breaking gpg signatures, not filed as a bug yet since I consider it
>   serious and want 2.1.4-3 to enter sarge.
 +1, I think it's already reported, at least I think it may be related to
#234540 .

> - Make the package lintian-clean, mostly requires fixing permissions.
 Yup, at least the trivial things should be done, dirs with permissions
of 2755!=0755 type of warnings.

> - Restructure the repository such that the package can be built with
>   svn-buildpackage w/o manual tweaking (maybe this is my fault, and
>   I'm overlooking some hidden option, atm I have to move upstream/ out
>   of the way to make it build).
 ? Haven't checked, but AFAIK upstream/ is OK to be there. Unfortunately
I do not have too much time nowadays. :(

Cheers,
Laszlo/GCS

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFAcX6ZMDatjqUaT90RAqt5AKCc1iRWTtXdsEETt8IfjOXAHRbp4QCfe+pM
FiirhoP7ZqS8s0u2os8Z4vY=
=O/0B
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--