Re: [SSI-devel] package management - yum?
Brought to you by:
brucewalker,
rogertsang
From: Brian J. W. <Bri...@hp...> - 2005-01-12 01:18:38
|
En Chiang Lee wrote: > Hi, > > I played around a little with yum, and installed a repository on my > desktop which has the SSI rpms in it. There's a problem with using it at > the moment... the kernel-ssi-rpm just has a dependency on cluster-tools > and openssi-tools and not on the rest of the packages. This was probably due to laziness on my part. ;) I think what we should do with the packages we enhance is say that each one "provides" something that the kernel-ssi RPM "requires". For example, our enhanced util-linux package could "provide" util-linux-ssi, which kernel-ssi could "require". This is better than making kernel-ssi explicitly depend on util-linux, which doesn't require it to be an SSI version of util-linux, or even worse making kernel-ssi depend on a specific SSI version of util-linux. > Also, if we > follow the install script, all the ssi-ized packages should be installed > and ssi-create run before installing the kernel rpm. It's not a hard requirement to follow the install script as it stand right now, but it is currently necessary that /etc/clustertab already exist before the kernel-ssi RPM is installed, so that it can properly build an initrd. > In the debian apt repository, Aneesh has created a dummy 'openssi' > package which depends on all the packages needed for openssi. I know Debian based systems like using dummy packages, as Aneesh has done. Is the same thing common with yum on Fedora/RH system? > However, > as Brian pointed out to me, debian packages let you run interactive > programs as part of the pre- and post-install scripts which are not > allowed in RPMS :-( Unfortunately, this seems to be the case. > If we put the input required by ssi-create in a configuration file and > have ssi-create read it from there in the post-install of openssi-tools, > we could use yum for our package management. The implication of this > would be that before doing 'yum install openssi' the configuration file > would have to be created. This would be part of the installation > instructions. > > We could also have a package which installs this file with values > detected using ifconfig, and then have the user make changes if > required. (This seems to be overkill though) > > Brian/Aneesh, what do you think? I don't like the idea of requiring a user to manually edit a configuration file, when we already have code for a user-friendly "interview" procedure. What would be preferable is breaking out this "interview" code from ssi-create, and making it a separate script that generates a configuration file for the user. Two other changes that come to mind are: 1) Making openssi-tools explicitly depend on the existence of this configuration file, so it won't partially install then fail in the post-install script when attempting to run ssi-create. 2) Making the kernel-ssi RPM explicitly depend on /etc/clustertab, so it won't partially install then fail in the post-install script when attempting to run mkinitrd. My 20 paise, Brian |