Philip Brown wrote: > Alan Coopersmith wrote: >> But they also seem to be trending away from single static config files shared >> by multiple packages that would require scripting to merge - for instance the >> Linux pam.d instead of Solaris's pam.conf, so packages can just drop in PAM >> configuration files without scripting, or the fontpath.d that Fedora >> invented, >> and we use also now, so we don't have to do mkfontdir or edit the font path >> in font package installation. > > contrariwise, handling font packages, even with SVR4, is trivial anyways. > You just deliver the files in some kind of "font" class, and have a class > action script run at the end. >
Except during live upgrade, when the older OS version needs to be able to handle the font actions on the new OS. Running OS-specific scripting for the new OS while running the old one causes problems, so don't do that. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
