On Wed, Apr 25, 2007 at 07:45:20AM -0700, Dermot McCluskey wrote: > Info file update service
Why is such an service needed? I can't actually see any problem in [un]installing info files as long as the installing host has a working 'install-info' (part of SUNWtexi). IMHO package *install scripts should handle the info files. Another service introduces just more overhead, buys nothing but makes managing the system more complicated. ... > In the SFW consolidation, Info documents are located in > /usr/sfw/share/info and /usr/share/info and each location > includes its own directory file, called "dir", covering > all the Info docs at that location. Currently, the > directory files are generated at build-time using the > "install-info" utility provided by texinfo(4). Yepp - bad practice. > All the > Info documents and the accompanying directory files for > the consolidation are then delivered together (in SUNWsfinf). Yepp - bad practice as well. It is pretty annoying, that SUN doesn't bundle the man/info pages with the package, they belong to ... So updating software (e.g. the castrated SUNWsndm*) with the fullblown stuff always leads to an unclean system (e.g. man pages need to be overwritten)... > The problem is that we now wish to deliver the Info docs > separately, as part of the relevant package. Also, > other consolidations, such as JDS, may wish to install > additional Info docs in the same locations and will > therefore need to update the directory files. Very good! > Install and remove Class Action Scripts that replicate > the work of install-info would prove excessively complex > and so a transient SMF service that rebuilds the directory > file when any Info docs are installed, removed or modified > is now proposed. Hmmm - disagree. IMHO it is rather easy! Actually one can use templates like *.manifest . A service wich needs to be adjusted every time a package is not installed in the default location makes the live not easier and as already said, its just overhead. I'm using two simple scripts, which create the appropriate *install script and never had a problem with any info dir for more than 5 years (neither on solaris nor linux ;-)). To give clue, here my usage pattern: http://dev.cs.uni-magdeburg.de/~elkner/pkg/Build.sh.sniplet.txt and the two simple scripts: http://dev.cs.uni-magdeburg.de/~elkner/pkg/createAddInfo.txt http://dev.cs.uni-magdeburg.de/~elkner/pkg/createRemoveInfo.txt So I would rather vote for "Include install-info in miniroots" and "Keep it small and simple" ... Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
