[softwaremgmt] Feature - running program at end of the instalations/on configure files conflict
Hi, I've been thinking about how to work with configuration files updates (feature #306411 [1]). In the end it seems that it would require some adjustments to installation system as well. I think it can be divided into two main features, so I'll post them here in two e-mails so it will be easier to track them. And the reason is of course to discuss there features, collect ideas and hopefully somebody will consider/implement them. Second thing that would be nice to have is some trigger which will get run after each installation/deinstallation/upgrade. Well, easiest way to implement feature #306411 is to use some script to collect conflicting configuration files after each installation and to display some warning that there are some conflicts that needs resolving. Warning should be easily possible to do, once previous feature would be supported. Other possibility how to achieve the same result would be some patch for rpm so it will generate such a message itself or calls something to "merge" conflicting files. I'm not sure what would be the best approach here. I can see some more generic usage of the first approach (like logging into mailbox or database), but I'm starting to think that second approach sounds better although patching rpm because of such a specific and probably minor feature also doesn't look like a good idea... [1] https://features.opensuse.org/306411 -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
Michal Hrusecky schrieb:
Hi,
I've been thinking about how to work with configuration files updates (feature #306411 [1]). In the end it seems that it would require some adjustments to installation system as well. I think it can be divided into two main features, so I'll post them here in two e-mails so it will be easier to track them. And the reason is of course to discuss there features, collect ideas and hopefully somebody will consider/implement them.
Second thing that would be nice to have is some trigger which will get run after each installation/deinstallation/upgrade. Well, easiest way to implement feature #306411 is to use some script to collect conflicting configuration files after each installation and to display some warning that there are some conflicts that needs resolving. Warning should be easily possible to do, once previous feature would be supported.
Other possibility how to achieve the same result would be some patch for rpm so it will generate such a message itself or calls something to "merge" conflicting files.
I'm not sure what would be the best approach here. I can see some more generic usage of the first approach (like logging into mailbox or database), but I'm starting to think that second approach sounds better although patching rpm because of such a specific and probably minor feature also doesn't look like a good idea...
Great, now we have a feature entry for Enh 506815 (https://bugzilla.novell.com/show_bug.cgi?id=506815). As a user I would basically think about an rpm integration as a good idea since I do still sometimes download and install/upgrade rpms manually. Besides this an rpm based patch would resolve our issue for zypper as well. Nonetheless a YaST/Opensuse updater/zypper integration will be of much greater value since I use these package management utilities most of the time. If the effort to supply both a GUI mechanism for YaST/OS-Updater and a textmode notification for rpm/zypper were not too high I would welcome both. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Hello, on Freitag, 12. Juni 2009, Michal Hrusecky wrote:
Second thing that would be nice to have is some trigger which will get run after each installation/deinstallation/upgrade. Well, easiest way to implement feature #306411 is to use some script to collect conflicting configuration files after each installation and to display some warning that there are some conflicts that needs resolving.
You mean like calling /etc/init.d/rpmconfigcheck ? ;-) If you want to add an additonal value, offer to run rpmresolve (see home:poeml, package servertools).
Other possibility how to achieve the same result would be some patch for rpm so it will generate such a message itself or calls something to "merge" conflicting files.
Hmm, I'm not sure if this feature is worth patching rpm. Including it in YaST / zypper should be enough. Regards, Christian Boltz -- Vielleicht habe ich ja Glück und fang mir eine tödliche Krankheit ein, dann kann ich das Rauchen wieder anfangen. [Ratti in fontlinge-devel] -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On Saturday 13 June 2009 23:23:26 Christian Boltz wrote:
Hello,
on Freitag, 12. Juni 2009, Michal Hrusecky wrote:
Second thing that would be nice to have is some trigger which will get run after each installation/deinstallation/upgrade. Well, easiest way to implement feature #306411 is to use some script to collect conflicting configuration files after each installation and to display some warning that there are some conflicts that needs resolving.
You mean like calling /etc/init.d/rpmconfigcheck ? ;-)
Or have a look at /var/log/YaST2/config_diff_*
If you want to add an additonal value, offer to run rpmresolve (see home:poeml, package servertools).
Other possibility how to achieve the same result would be some patch for rpm so it will generate such a message itself or calls something to "merge" conflicting files.
Hmm, I'm not sure if this feature is worth patching rpm. Including it in YaST / zypper should be enough.
Rpm issues such a warning if you use -v. libzypp checks this and creates the above diffs for YaST. But it's not a problem to collect this info and invoke some consumer script at the end of commit. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
participants (4)
-
Christian Boltz -
Elmar Stellnberger -
Michael Andres -
Michal Hrusecky