* Jimmy Engelbrecht [2004-04-07 18:44:04 +0200]: > Derrick J Brashear <[EMAIL PROTECTED]> writes: > > > Are the packaging scripts worth integrating into src/packaging? > > What script ? :-)
So it sounds like there is more work to be done. To really fit into the Solaris way of doing things, one should have several packages: -- a separate package for the 64-bit components (kernel module), to be omitted on pure 32-bit installs (and for OpenAFS there is the additional choice of full vs. nonfs modules, which may justify another pair of packages); -- separate packages for the client and server utilities (i.e. one should be able to not even install the *server binaries on clients); -- one or more separate packages for the development stuff (header files, static libs, etc.) Many Solaris package sets are also split along *u/*r (User/Root) lines, with the *r package usually including startup scripts and/or configuration files. I'm not sure this is useful for OpenAFS, though (unlike the previous suggestions, which will help conserve disk space). Look at Solaris 9's SUNWnfs{c,s}{r,u,x} split for possible guidance. _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info