On Thu, May 19, 2005, Frank Torres wrote:
> I have created few extra options in this rpm that fixes and or enhances
> mailman:
>
> 1. I have removed the private.py patch in the mailman.patch file.
> a. I am using the official patch from mailman:
> http://www.gnu.org/software/mailman/CAN-2005-0202.txt
Ok, good idea. Taken over.
> 2. I replaced how mailman displays the owner of list in the web
> interface I personally did like having the actual owners
> e-mail addresses listed. It's better to list the
> {listname}-owner. I think this makes more sense.
Ok, also a reasonable idea and similar to other mailing list
managers. Taken over, too.
> 3. I have eliminated the icon that displayed what version of mailman is
> running at the bottom of each web page. Again I do not believe this
> to be necessary. And since Mailman is Open Source this should be
> fine to not display it.
Hmmm... I see neither a great problem in removing it nor a great benefit
in removing it. So, I've still not taken this over.
> 4. I added with_yourimage this will replace the PythonPowered.png file
> with whatever logo you wish to have at the bottom of the web page.
> Please note that this is with_out the NoSource option so you have
> to build/rebuild with source in order to take advantage of this
> feature.
I always try to avoid the %NoSource functionality as it makes lots of
problems and especially currently is a showstopper for all packages
which should be part of a release. Additionally, this change isn't such
important IMHO, so I've still not taken it over.
> 5. I also made a small change to mm-handler for sendmail so that
> all requests of the address are in lower case. The reason this
> is done is that I noticed that upper case characters were problems
> for mailman so I just eliminated all upper case altogether.
Well, the addresses are just case-sensitive. If you lower-case all
addresses you no longer can have lists with upper-case characters in the
name. Hence I currently better don't want to take this over.
The remaining changes you've made for making the user/group configurable
I've also not taken over as it is a little bit against the general
principle of having all OpenPKG packages fit together and of having the
OpenPKG instance fully self-contained. The default user/group should
fit what the MTAs expect, shouldn't it? If we allow the user/group to
be changed, a totally different package comes out which mainly exists
just to integrate better with software _outside_ OpenPKG, right? I see
the motivation for adding this flexibility, but OTOH if we go into this
direction for the "mailman" package, why are we not doing it also for
all other packages? If we really need this flexibility, I think a more
general solution (perhaps doing a "--rebuild --musr foo --mgrp foo")
should be provided...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
