Here are the minutes from our last meeting, Andreas * PolicyKit/resmgr The upstream Hal authors are preparing to require PolicyKit. PolicyKit is a system daemon, applications ask the daemon about permissions. This is a similar concept as resmgr. The question is how to move forward for our distribution. Will be further discussed next time. * Starting daemons by default A reminder: Daemons will only be started by default from their packages if the dist meeting has approved this. Otherwise the autobuild team is authorized to reject this. PolicyKit is a new daemon, it was approved to be started for now. * Move to GNOME 2.16 Not discussed since nobody involved attended, postponed for next meeting (or discussion via email). * SuSEconfig removal SuSEconfig is currently run after each package installation by YaST and is a huge bottleneck. Some scripts have already been removed and we have to discuss how to move on. The purpose of SuSEconfig was to not run one script several times during package installation but just once at the end. We plan to fix scripts that can be done differently, remove obsolete ones and the autobuild team will not check in new SuSEconfig scripts. A review of scripts showed that some are really obsolete, the first 5 scripts were removed already. We need a superior solution, e.g. some way to do delayed execution. This should also work if just rpm or smart is used. An overview of SuSEconfig is appended below. * update messages general/conditional (e.g. bind) During update of packages they could notify users about changes via email and/or the SuSEplugger (until 10.0, this is not anymore in 10.1). Most of these are outdated and not really usefull anymore and should be removed. The question is how to handle situations like bind where config files get rewritten and the user should be informed if this fails. In general, it is not possible to send emails from rpm install scripts. Most cases could be handled by the release notes but there are cases that cannot and we need a better solution to present this, especially since many people to not read the local emails. * Dropping UP Kernel on i386/x86-64 No objection by the dist meeting. This should be done for Alpha4. * Linker Options and Optimizations LDFLAGS="-Wl,-z relro" is now the default and works fine. The hash table optimization will be enabled in binutils and glibc by default as well. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SUSEconfig has around 4 classes of different scripts, the first two are the most common cases: a) /etc/sysconfig has two types of data. * data read by rc-scripts and used directly there * data used by SuSEconfig and spread over /etc/* or /var/* The second type is handled by one class of SuSEconfig scripts, called "CLASS-A". Solutions: - extend rc-scripts to do this - extend daemons to read /etc/sysconfig - ... b) directory index caches scripts that keep index files in several directories up to date. The underlying problem is that rpm can not trigger based on directory modification, but that's currently not in sight. In many cases SuSEconfig is just the cheap solution. A related problem is, that if you install 10 packages, you don't want to regenerate these indexes 10 times. Solutions: - call individually in each related package (the "install-info way") - error prone - many modifications to many packages (and over again for any change) - extend usage of these index files to update cache themselves - ... This type will be called CLASS-B below. (some of these have also been moved to cron.daily in the past) c) similar to b but generate other filetypes from installed files, usually hacks for special programs CLASS-C d) set a symlink according to installation CLASS-D (probably easiest for a postinstall solution) (modulename) (packagename) (class) SuSEconfig.automake (automake) CLASS-B SuSEconfig.cjk-latex (cjk-latex) CLASS-C SuSEconfig.desktop-file-utils (desktop-file-utils) CLASS-B SuSEconfig.fonts (fonts-config) CLASS-B (mostly) SuSEconfig.gdm (gdm) CLASS-A SuSEconfig.ghostscript-cjk (ghostscript-cjk) CLASS-A? SuSEconfig.gnome-vfs2 (gnome-vfs2) CLASS-B SuSEconfig.groff (groff) CLASS-A SuSEconfig.gtk2 (gtk2) CLASS-B SuSEconfig.guile (guile) CLASS-B SuSEconfig.icu (icu) CLASS-D SuSEconfig.isdn (i4l-base) CLASS-A SuSEconfig.ispell (ispell) CLASS-A/CLASS-D SuSEconfig.kde (kdebase3-NLD,kdebase3-SuSE) CLASS-A SuSEconfig.kdm3 (kdebase3-NLD,kdebase3-SuSE) CLASS-A SuSEconfig.libxml2 (libxml2) CLASS-B SuSEconfig.lyx-cjk (cjk-lyx) CLASS-B SuSEconfig.mailman (mailman) CLASS-A SuSEconfig.news (aaa_base) CLASS-A SuSEconfig.pango (pango) CLASS-B SuSEconfig.pbs (OpenPBS) CLASS-A SuSEconfig.perl (perl) CLASS-B SuSEconfig.permissions (permissions) CLASS-A (special ...) SuSEconfig.postfix (postfix) CLASS-A SuSEconfig.prelink (prelink) CLASS-B SuSEconfig.scim (scim) CLASS-A SuSEconfig.scpm (scpm) ?? (-> rcscript .. ?) SuSEconfig.scrollkeeper (scrollkeeper) CLASS-B SuSEconfig.sendmail (sendmail) CLASS-A SuSEconfig.susehelp (susehelp) CLASS-A(?) SuSEconfig.syslog-ng (syslog-ng) CLASS-A SuSEconfig.tetex (tetex) CLASS-B SuSEconfig.tuxpaint (tuxpaint) CLASS-C SuSEconfig.wdm (wdm) CLASS-A SuSEconfig.words (words) CLASS-A/CLASS-D SuSEconfig.xdm (xorg-x11) CLASS-A SuSEconfig.xjdic (xjdic-indices) CLASS-B SuSEconfig.xpdf (xpdf-tools) CLASS-B(?) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126