On Fri, 4 Mar 2011 10:57:35 -0500
Jack Neely <jjneely(a)ncsu.edu> wrote:
it looks like the proper thing to do is include these
static libraries in the -devel sub-package and have that
sub-package provide openafs-static.
Secondly, many more experienced AFS administrators prefer
the old Transarc style paths over the FHS paths that my
packages use. I would like to create an openafs-transarc
sub-package that includes the symlinks that would enable
these non-standard paths. (Specifically, /usr/afs
and /usr/vice.)
The first issue with the static libs really needs to
happen. The second issue is just pure annoyance but will
make these packages more usable to certain folks. I'd like
to do both. Are there any comments or reason why I should
not?
Jack Neely
Both sound good to me (yes, the FHS is a nice ideal, but a
compat package with "DEPRECATED" somewhere in the description
is an ok crutch). And as Ralf has so helpfully pointed out,
not even RH follows the FHS 100%.
--
Conrad Meyer <cemeyer(a)cs.washington.edu>