[fedfs-utils/el6] First try at packaging for el6 (EPEL)

Chuck Lever mrchuck at fedoraproject.org
Mon Sep 16 20:31:09 UTC 2013 

commit bb5b49dc5decb57e9ef0454ca0e1c005b05b1325
Author: Chuck Lever <chuck.lever at oracle.com>
Date:   Mon Sep 16 16:30:19 2013 -0400

    First try at packaging for el6 (EPEL)
    
    - Update to fedfs-utils-0.9.3 in order to build without liburiparser
    - None of the fedfs-utils server components work with nfs-utils or
      kernel in EL6
    - fedfs-utils admin components not needed in EL6
    - EL6 autofs does not support /etc/auto.master.d directory

 .gitignore       |    1 +
 fedfs-utils.spec |  314 ++++++++---------------------------------------------
 sources          |    2 +-
 3 files changed, 50 insertions(+), 267 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 67744e6..33484bf 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
 /fedfs-utils-0.9.0.tar.gz
 /fedfs-utils-0.9.1.tar.gz
 /fedfs-utils-0.9.2.tar.gz
+/fedfs-utils-0.9.3.tar.gz
diff --git a/fedfs-utils.spec b/fedfs-utils.spec
index 7507937..94d8197 100644
--- a/fedfs-utils.spec
+++ b/fedfs-utils.spec
@@ -1,36 +1,37 @@
 Name:           fedfs-utils
-Version:        0.9.2
-Release:        3%{?dist}
+Version:        0.9.3
+Release:        2%{?dist}
 Summary:        Utilities for mounting and managing FedFS
 
 Group:          System Environment/Daemons
 License:        GPLv2
 URL:            http://wiki.linux-nfs.org/wiki/index.php/FedFsUtilsProject
 BuildRequires:  libidn-devel libattr-devel libcap-devel openldap-devel
-BuildRequires:  sqlite-devel libtirpc-devel libuuid-devel systemd-units
-BuildRequires:  openssl-devel libxml2-devel uriparser-devel
+BuildRequires:  sqlite-devel libtirpc-devel libuuid-devel
+BuildRequires:  openssl-devel libxml2-devel libgssglue-devel
 
 Source0:        http://oss.oracle.com/projects/%{name}/dist/files/%{name}-%{version}.tar.gz
 
-%global unit_name rpcfedfsd
+%global _hardened_build 1
 %define debug_package %{nil}
 
 %description
 RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
 is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
+construct a coherent file name space across multiple file servers using
+file system referrals.
 
 A file system referral is like a symbolic link to another file system
 share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
+auto-mounted directory where a new file system mount is done when an
 application first accesses that directory. The arguments of the mount
 operation are controlled by information returned by the file server.
 
 Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
+system protocols. FedFS provides its file name space features by
+leveraging referral mechanisms already built in to network file system
+protocols.  Thus no change to file system protocols or clients is
+required.
 
 Currently, the Linux FedFS implementation supports only NFS version 4
 referrals. More on NFS version 4 referrals can be found in RFC 3530.
@@ -40,23 +41,21 @@ FedFS may support other network file system protocols in the future.
 %setup -q -n %{name}-%{version}
 
 %build
-%configure --prefix=/usr
+%configure --prefix=/usr --without-liburiparser
 make %{?_smp_mflags}
 
 %install
-make install DESTDIR=%{buildroot}
-mkdir -p %{buildroot}%{_sharedstatedir}/fedfs
-mkdir -p %{buildroot}%{_unitdir}
+( cd src/mount; make install DESTDIR=%{buildroot} )
+( cd doc/man; make install DESTDIR=%{buildroot} )
+rm -f %{buildroot}%{_mandir}/man7/nsdb-*
+rm -f %{buildroot}%{_mandir}/man8/fedfs-{create,delete,get,lookup,null,set}*
+rm -f %{buildroot}%{_mandir}/man8/nfsref*
+rm -f %{buildroot}%{_mandir}/man8/nsdb*
+rm -f %{buildroot}%{_mandir}/man8/rpc.fedfs*
 mkdir -p %{buildroot}/nfs4
-install -m 644 contrib/init/%{unit_name}.service %{buildroot}%{_unitdir}
-mkdir -p %{buildroot}%{_sysconfdir}/sysconfig
-install -m 644 contrib/init/fedfs %{buildroot}%{_sysconfdir}/sysconfig
-mkdir -p %{buildroot}/etc/auto.master.d
-install -m 644 contrib/init/fedfs.autofs %{buildroot}/etc/auto.master.d
 
-# Don't package static libs to encourage use of shared library.
-rm -f %{buildroot}%{_libdir}/libnfsjunct.a
-rm -f %{buildroot}%{_libdir}/libnfsjunct.la
+%clean
+rm -rf %{buildroot}
 
 %package common
 Summary:      Common files for FedFS
@@ -67,25 +66,27 @@ This package contains files common to all of the fedfs packages.
 
 RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
 is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
+construct a coherent file name space across multiple file servers using
+file system referrals.
 
 A file system referral is like a symbolic link to another file system
 share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
+auto-mounted directory where a new file system mount is done when an
 application first accesses that directory. The arguments of the mount
 operation are controlled by information returned by the file server.
 
 Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
+system protocols. FedFS provides its file name space features by
+leveraging referral mechanisms already built in to network file system
+protocols.  Thus no change to file system protocols or clients is
+required.
 
 Currently, the Linux FedFS implementation supports only NFS version 4
 referrals. More on NFS version 4 referrals can be found in RFC 3530.
 FedFS may support other network file system protocols in the future.
 
 %files common
+%defattr(-,root,root,-)
 %doc COPYING README INSTALL ChangeLog doc/ldap/fedfs.schema doc/ldap/fedfs-schema.ldif
 %{_mandir}/man7/fedfs.7.*
 
@@ -94,267 +95,48 @@ Summary:      Utilities for mounting FedFS domains
 Group:        System Environment/Daemons
 Requires:     %{name}-common = %{version}-%{release}
 Requires:     nfs-utils autofs
-Requires(post): systemd-units
-Requires(postun): systemd-units
+
 %description client
 This package contains the tools needed to mount a FedFS domain and act
-as a client.
+as a FedFS file system client.
 
 RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
 is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
+construct a coherent file name space across multiple file servers using
+file system referrals.
 
 A file system referral is like a symbolic link to another file system
 share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
+auto-mounted directory where a new file system mount is done when an
 application first accesses that directory. The arguments of the mount
 operation are controlled by information returned by the file server.
 
 Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
+system protocols. FedFS provides its file name space features by
+leveraging referral mechanisms already built in to network file system
+protocols.  Thus no change to file system protocols or clients is
+required.
 
 Currently, the Linux FedFS implementation supports only NFS version 4
 referrals. More on NFS version 4 referrals can be found in RFC 3530.
 FedFS may support other network file system protocols in the future.
 
 %files client
+%defattr(-,root,root,-)
 /sbin/mount.fedfs
 %{_sbindir}/fedfs-map-nfs4
 %{_mandir}/man8/mount.fedfs.8.*
 %{_mandir}/man8/fedfs-map-nfs4.8.*
 %dir /nfs4
-%config(noreplace) /etc/auto.master.d/fedfs.autofs
-
-%post client
-# We may have changed the automounter configuration
-/bin/systemctl reload autofs.service >/dev/null 2>&1 || :
-
-%postun client
-# We may have changed the automounter configuration
-/bin/systemctl reload autofs.service >/dev/null 2>&1 || :
-
-%package nsdbparams
-Summary:      The FedFS nsdbparams utility
-Group:        System Environment/Daemons
-Requires:     %{name}-common = %{version}-%{release}
-%description nsdbparams
-This package contains the nsdbparams utility, which manages the
-NSDB connection parameters used during FedFS junction resolution
-and domain administration.
-
-RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
-is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
-
-A file system referral is like a symbolic link to another file system
-share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
-application first accesses that directory. The arguments of the mount
-operation are controlled by information returned by the file server.
-
-Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
-
-Currently, the Linux FedFS implementation supports only NFS version 4
-referrals. More on NFS version 4 referrals can be found in RFC 3530.
-FedFS may support other network file system protocols in the future.
-
-%files nsdbparams
-%{_sbindir}/nsdbparams
-%{_mandir}/man8/nsdbparams.8.*
-%{_mandir}/man7/nsdb-parameters.7.*
-
-%package devel
-Summary:      Development files for the FedFS nfs-plugin
-Group:        System Environment/Daemons
-Requires:     %{name}-lib%{?_isa} = %{version}-%{release}
-%description devel
-This package contains development files for the FedFS nfs-plugin
-library.  This package must be present at nfs-utils build time for
-NFS and FedFS junction support to be enabled in nfs-utils.
-
-RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
-is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
-
-A file system referral is like a symbolic link to another file system
-share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
-application first accesses that directory. The arguments of the mount
-operation are controlled by information returned by the file server.
-
-Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
-
-Currently, the Linux FedFS implementation supports only NFS version 4
-referrals. More on NFS version 4 referrals can be found in RFC 3530.
-FedFS may support other network file system protocols in the future.
-
-%files devel
-%{_includedir}/nfs-plugin.h
-
-%package lib
-Summary:      The FedFS nfs-plugin run-time library
-Group:        System Environment/Daemons
-Requires:     %{name}-common = %{version}-%{release}
-Requires:     %{name}-nsdbparams%{?_isa} = %{version}-%{release}
-%description lib
-This package contains the FedFS nfs-plugin run-time library.  This
-package must be installed for FedFS junction support to be enabled in
-rpc.mountd.
-
-RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
-is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
-
-A file system referral is like a symbolic link to another file system
-share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
-application first accesses that directory. The arguments of the mount
-operation are controlled by information returned by the file server.
-
-Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
-
-Currently, the Linux FedFS implementation supports only NFS version 4
-referrals. More on NFS version 4 referrals can be found in RFC 3530.
-FedFS may support other network file system protocols in the future.
-
-%post lib -p /sbin/ldconfig
-
-%postun lib -p /sbin/ldconfig
-
-%files lib
-# We need to include this in the lib package because it is
-# dlopen()ed by the junction support code in nfs-utils.
-%{_libdir}/libnfsjunct.so
-%{_libdir}/libnfsjunct.so.*
-
-%package server
-Summary:      Utilities for serving FedFS domains
-Group:        System Environment/Daemons
-Requires:     %{name}-common = %{version}-%{release}
-Requires:     %{name}-nsdbparams%{?_isa} = %{version}-%{release}
-Requires:     %{name}-lib%{?_isa} = %{version}-%{release}
-Requires:     nfs-utils
-Requires(post):   systemd-units
-Requires(preun):  systemd-units
-Requires(postun): systemd-units
-
-%description server
-This package contains tools for managing NFS and FedFS junctions
-on a Linux NFS fileserver.
-
-RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
-is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
-
-A file system referral is like a symbolic link to another file system
-share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
-application first accesses that directory. The arguments of the mount
-operation are controlled by information returned by the file server.
-
-Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
-
-Currently, the Linux FedFS implementation supports only NFS version 4
-referrals. More on NFS version 4 referrals can be found in RFC 3530.
-FedFS may support other network file system protocols in the future.
-
-%pre server
-getent group fedfs >/dev/null || groupadd -r fedfs
-getent passwd fedfs >/dev/null || \
-    useradd -r -g fedfs -d %{_sharedstatedir}/fedfs -s /sbin/nologin \
-    -c "FedFS Server User" fedfs
-exit 0
-
-%post server
-%systemd_post %{unit_name}.service
-
-%preun server
-%systemd_preun %{unit_name}.service
-
-%postun server
-%systemd_postun_with_restart %{unit_name}.service
-
-%files server
-%dir %{_sharedstatedir}/fedfs
-%{_sbindir}/nfsref
-%{_sbindir}/rpc.fedfsd
-%{_mandir}/man8/rpc.fedfsd.8.*
-%{_mandir}/man8/nfsref.8.gz
-%{_unitdir}/rpcfedfsd.service
-%config(noreplace) %{_sysconfdir}/sysconfig/fedfs
-
-%package admin
-Summary:      Utilities for administering FedFS domains
-Group:        System Environment/Daemons
-Requires:     %{name}-common = %{version}-%{release}
-Requires:     %{name}-nsdbparams%{?_isa} = %{version}-%{release}
-%description admin
-This package contains the tools needed to manage a FedFS domain.
-
-RFC 5716 introduces the Federated File System (FedFS, for short). FedFS
-is an extensible standardized mechanism by which system administrators
-construct a coherent namespace across multiple file servers using file
-system referrals.
-
-A file system referral is like a symbolic link to another file system
-share, but it is not visible to applications. It behaves like an
-automounted directory where a new file system mount is done when an
-application first accesses that directory. The arguments of the mount
-operation are controlled by information returned by the file server.
-
-Today, file system referral mechanisms exist in several network file
-system protocols. FedFS provides its namespace features by leveraging
-referral mechanisms already built in to network file system protocols.
-Thus no change to file system protocols or clients is required.
-
-Currently, the Linux FedFS implementation supports only NFS version 4
-referrals. More on NFS version 4 referrals can be found in RFC 3530.
-FedFS may support other network file system protocols in the future.
-
-%files admin
-%{_sbindir}/fedfs-create-junction
-%{_sbindir}/fedfs-create-replication
-%{_sbindir}/fedfs-delete-junction
-%{_sbindir}/fedfs-delete-replication
-%{_sbindir}/fedfs-get-limited-nsdb-params
-%{_sbindir}/fedfs-get-nsdb-params
-%{_sbindir}/fedfs-lookup-junction
-%{_sbindir}/fedfs-lookup-replication
-%{_sbindir}/fedfs-null
-%{_sbindir}/fedfs-set-nsdb-params
-%{_sbindir}/nsdb-*
-%{_mandir}/man8/fedfs-create-junction.8.*
-%{_mandir}/man8/fedfs-create-replication.8.*
-%{_mandir}/man8/fedfs-delete-junction.8.*
-%{_mandir}/man8/fedfs-delete-replication.8.*
-%{_mandir}/man8/fedfs-get-limited-nsdb-params.8.*
-%{_mandir}/man8/fedfs-get-nsdb-params.8.*
-%{_mandir}/man8/fedfs-lookup-junction.8.*
-%{_mandir}/man8/fedfs-lookup-replication.8.*
-%{_mandir}/man8/fedfs-null.8.*
-%{_mandir}/man8/fedfs-set-nsdb-params.8.*
-%{_mandir}/man8/nsdb-*
 
 %changelog
+* Mon Sep 16 2013 Chuck Lever <chuck.lever at oracle.com> - 0.9.3-2
+- Packaging for el6 (EPEL)
+- Update to fedfs-utils-0.9.3 in order to build without liburiparser
+- None of the fedfs-utils server components work with nfs-utils or kernel in EL6
+- fedfs-utils admin components not needed in EL6
+- EL6 autofs does not support /etc/auto.master.d directory
+
 * Sat Aug 03 2013 Fedora Release Engineering <rel-eng at lists.fedoraproject.org> - 0.9.2-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
 
@@ -417,7 +199,7 @@ FedFS may support other network file system protocols in the future.
 * Mon Dec 5 2011 Ian Kent <ikent at redhat.com> 0.7.3-2
 - add systemd-units to BuildRequires as per systemd doco.
 
-* Fri Nov 30 2011 Jeff Layton <jlayton at redhat.com> 0.7.3-1
+* Wed Nov 30 2011 Jeff Layton <jlayton at redhat.com> 0.7.3-1
 - update to 0.7.3 release
 
 * Fri Nov 04 2011 Jeff Layton <jlayton at redhat.com> 0.7.2-1
diff --git a/sources b/sources
index 3c0d469..5490400 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-9eabf1b98e564c50fc45a1e03e0a0da3  fedfs-utils-0.9.2.tar.gz
+d1ed17f482103ce629f2439ddc9ab251  fedfs-utils-0.9.3.tar.gz

More information about the scm-commits mailing list