http://qa.mandrakesoft.com/show_bug.cgi?id=6207


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|                            |UNCONFIRMED




------- Additional Comments From [EMAIL PROTECTED]  2003-10-23 18:31 -------
That is mostly an upstream problem. Some times ago, the question could also 
have been: why is configuration in /var/lib ?  
  
Default mailman install use a single top-level directory install, usually in  
/var/lib. However, it also allows a configure option to split files between  
variables files, that goes in /var/lib, and non-variables files, that goes in  
/usr/share, wich is standard Unix setup. I recently switched the package to  
use the latest setup.  
  
However, configuration in mailman, as in many python software, takes the form  
of a python source file. msec does the same, for instance. But msec place this  
file in /etc, with write access for python to keep the compiled version,  
whereas mailman keep it in /usr/share among other python source files. Maybe  
just using symlink would be OK, otherwise we would have to ask the developper  
to allows mm_cfg.py to be in /etc instead.  
  
BTW, mailman is not the only one software to use non-standard location for  
configuration files. Most webapps does the same, whereas they have some sort  
of cross-platform compatibility excuse. KDE does also the same, and use  
/usr/share/config, and I never saw any actual reason for this, as it is pure  
Unix software... 

------- Additional Comments From [EMAIL PROTECTED]  2003-10-27 06:47 -------
And one more thing - your own post-unstall script look for mmsitepass in /var!!

---8<-----------------------------------------------
# rpm -Uhv ../RPMS/mailman-2.1.2-9mdk.i586.rpm 
Preparing...                ########################################### [100%]
   1:mailman                ########################################### [100%]
Post-install compilation...
Reloading httpd2: [  OK  ]

*****
* You must now "cd /usr/lib/mailman/" and run "bin/mmsitepass" as root to set the
* site password to be used for administrating all Mailman data as necessary.
*****

*****
* You must also "cd /usr/lib/mailman/" and run "bin/newlist mailman" as root to
* setup the base mailman maillist - answer the questions appropriately.
*****

/var/tmp/rpm-tmp.62463: line 3: /var/lib/mailman/bin/mmsitepass: 
                                 ^^^ -- are you tested mailman installation?
No such file or directory
---------------------------------------------------------------->8--



About changelog:
--8<------------------------------------------------
# rpm -q --changelog mailman    
...
* Mon Sep 08 2003 Guillaume Rousse <[EMAIL PROTECTED]> 2.1.2-7mdk
...
- constant files under /usr/lib/mailman, variable files under /var/lib/mailman
...
------------------------------------------------>8--



About "mm_cfg.py to me is questionable as a pure config file":
This file needed for us - Plesk Control Panel use it for mailman configure.  On
Mandrake Linux 9.2 RC1 our product works, but on Mandrake Linux 9.2 Release -
not.  How we can explain for our customers why Plesk doesn't work on Mandrake
Linux 9.2?  Plesk included in Mandrake Linux, therefore Plesk must work on
Mandrake Linux.

Ok, sorry for emotions.
Please, tell me your decision - you rollback path to /var directory, or not?  We
must release Plesk 6.0.2, and if you not plane to change mailman2.1.2-9, we
change path in ours utilities for mailman reconfigure.  This is a serious
problem - one of our features is not work at all.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
# rpm -q --changelog mailman
- constant files under /usr/lib/mailman, variable files under /var/lib/mailman

# rpm -ql mailman | grep mm_c
/usr/lib/mailman/Mailman/mm_cfg.py

WTF?  Why config of mailman (mm_cfg.py) abide in /usr/ ?  
          ^^^^^^

man hier says:
/usr   This directory is usually mounted from a separate partition.  It should
hold only sharable, read-only data, so  that  it  can  be mounted by various
machines running Linux.

I use my own script for reconfiguring mailman config.  Now my script is not
right - /usr may be read-only mounted, for example.

As I know, all configs must be in /etc directory.

PS: also I not like the next fact - in MandrakeLinux 9.2 rc1 mailman config
abide in /var, but in release it shange its place - this is not good thing.

Reply via email to