* Volker A. Brandt <[EMAIL PROTECTED]> [2008-09-21 20:40]: > Hello Stephen! > > > > I am working out a more general file assembly > > mechanism. > > This is good to hear. I have the following use case: Many of my > packages are open source tools "wrapped up" for easy installation. > A lot of these contain info files as documentation. > > I've written a CAS "i.info" that drops the info files into place > and then calls the install-info script on them, which will add entries > in the info "dir" file at the appropriate spots. The "i.info" CAS > also creates the counterpart "r.info" CAS to delete the entries > upon package removal. > > I install these packages both on "running" systems and during > custom jumpstart. > > Will your file assembly mechanism cover this use case? Or would > I basically have to replicate the functionality of the "install-info" > script?
I believe this use case is handled by actuators in concert with Dermot's info file update service http://mail.opensolaris.org/pipermail/smf-discuss/2007-April/006367.html although perhaps just being able to customize the info_dir_path isn't sufficient? At least, that's how we believe manual page indices and infodir files can be handled. - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
