On Sat, Mar 05, 2011 at 06:45:37PM -0800, Conrad Meyer wrote:
> On Fri, 4 Mar 2011 10:57:35 -0500
> Jack Neely 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, ma
On Fri, 4 Mar 2011 10:57:35 -0500
Jack Neely 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
On 03/04/2011 06:28 PM, Ken Dreyer wrote:
On Fri, Mar 4, 2011 at 9:08 AM, Ralf Corsepius wrote:
Because this "transarc style" doesn't comply to the FHS.
I think FHS is a good thing to have. Several packages have exceptions,
They don't have an exception, they are broken rsp. certain people
On Fri, Mar 04, 2011 at 10:28:44AM -0700, Ken Dreyer wrote:
> On Fri, Mar 4, 2011 at 9:08 AM, Ralf Corsepius wrote:
> >
> > Because this "transarc style" doesn't comply to the FHS.
>
> I think FHS is a good thing to have. Several packages have exceptions,
> eg. krb5-workstation
>
> $ rpm -ql krb
On Fri, Mar 4, 2011 at 9:08 AM, Ralf Corsepius wrote:
>
> Because this "transarc style" doesn't comply to the FHS.
I think FHS is a good thing to have. Several packages have exceptions,
eg. krb5-workstation
$ rpm -ql krb5-workstation
/usr/kerberos
/usr/kerberos/bin
/usr/kerberos/bin/k5srvutil
/u
On 03/04/2011 04:57 PM, Jack Neely wrote:
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.
Folks,
I have two quandaries about my OpenAFS packages. Both of which are a
bit problematic when trying to conform to the Fedora Packaging
Guidelines.
OpenAFS has a slew of static libraries that are part of upstream's
packages and used for just about anything that uses OpenAFS's C API,
such as t
