Home_greyopenFATE - openSUSE feature tracking > #313540
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Get rid of SuSEconfig.mailman

Feature state

openSUSE Distribution
Done

Description

There is no point to run that code after installation of every package
(and it's not run when you use zypper or 3rd party tools anyways). That
code should be only run as a part of post-install of the mailman
packages as only those are affected.

Relations

Discussion


icons/user_comment.png C. B. wrote: (5 years ago)

SuSEconfig.mailman has/had to be run after changing /etc/sysconfig/mailman (but not in %post or something like that)

https://build.opensuse.org/request/show/136611 comes with this .changes entry:

- removed SuSEconfig dependency * SuSEconfig.mailman is moved to a new location, and works pretty much the same way as before. which may or may not be a good thing, perhaps this functionality should be removed completely

I tend to the "may not" part ;-) - the better solution would be if mailman reads the sysconfig file at startup.

icons/user_comment.png J. M. wrote: (5 years ago)

> the better solution would be if mailman reads the sysconfig file at startup.

Not really. Of course, we could make this script a part of service startup entry. But let's see, do we have a feature or customer usecase for that? ;e)

The way I see it, users can configure their mailman installation using mailman's own config files - which they would have to do anyway if they wanted to modify something beyond what sysconfig covers. I'm not sure why the sysconfig functionality was originally added and i'm not aware of any benefits over configuring mailman directly (esp. since you have to run mailman-generate-sysconfig afterwards).
So perhaps we should stop pretending that sysconfig somehow does a better job and instead provide instructions for the source config file?

icons/user_comment.png C. B. wrote: (5 years ago)

Well, there are two ways:

a) make sure the sysconfig file is read by mailman - for example in the initscript/.service file so that changes become active when mailman is (re)started

b) drop the sysconfig file and let admins change the mailman config directly

Both ways are good, even if they are totally different. And you are right that people will need to change the mailman config file if they want to change options not covered by sysconfig.

The problem with the current way is that it's somewhere in between. I'm afraid most people won't see the "you have to run $SCRIPT afterwards" (which means the changes in sysconfig aren't applied) and they will just complain that this @§&$%§% sysconfig file doesn't work ;-)

icons/user_comment.png M. V. wrote: (5 years ago)

If that's done for openSUSE, this will be shared by SLE-12, so marked as done as well.

Last change: 5 years ago
Voting
Score: 1
  • Negative: 0
  • Neutral: 0
  • Positive: 1
Tags
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint