From f3ca4fadd0312a4b1a01dc844ba520646e22c483 Mon Sep 17 00:00:00 2001
From: CentOS Sources <bugs@centos.org>
Date: Apr 10 2018 09:38:42 +0000
Subject: import driverctl-0.95-1.el7


---

diff --git a/.driverctl.metadata b/.driverctl.metadata
new file mode 100644
index 0000000..da22492
--- /dev/null
+++ b/.driverctl.metadata
@@ -0,0 +1 @@
+04bc30cb1c12d2d79f01603bf35d5b8784d18260 SOURCES/driverctl-0.95-3c668744f2242e453fdcd6dca36d3e1d82d0367a.tar.gz
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..2629d3f
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+SOURCES/driverctl-0.95-3c668744f2242e453fdcd6dca36d3e1d82d0367a.tar.gz
diff --git a/README.md b/README.md
deleted file mode 100644
index 98f42b4..0000000
--- a/README.md
+++ /dev/null
@@ -1,4 +0,0 @@
-The master branch has no content
-
-Look at the c7 branch if you are working with CentOS-7, or the c4/c5/c6 branch for CentOS-4, 5 or 6
-If you find this file in a distro specific branch, it means that no content has been checked in yet
diff --git a/SPECS/driverctl.spec b/SPECS/driverctl.spec
new file mode 100644
index 0000000..31ab16b
--- /dev/null
+++ b/SPECS/driverctl.spec
@@ -0,0 +1,75 @@
+%global commit	3c668744f2242e453fdcd6dca36d3e1d82d0367a
+
+Name:		driverctl
+Version:	0.95
+Release:	1%{?dist}
+Summary:	Device driver control utility
+
+Group:		System Environment/Kernel
+License:	LGPLv2
+URL:		https://gitlab.com/driverctl/driverctl
+BuildArch:	noarch
+
+# rpm doesn't grok the gitlab url but spectool understands this monster
+Source0:	https://gitlab.com/driverctl/%{name}/repository/archive.tar.gz?ref=%{version}#/%{name}-%{version}-%{commit}.tar.gz
+
+# for udev macros
+BuildRequires: systemd
+Requires(post,postun): %{_sbindir}/udevadm
+Requires: coreutils udev
+
+%description
+driverctl is a tool for manipulating and inspecting the system
+device driver choices.
+
+Devices are normally assigned to their sole designated kernel driver
+by default. However in some situations it may be desireable to
+override that default, for example to try an older driver to
+work around a regression in a driver or to try an experimental alternative
+driver. Another common use-case is pass-through drivers and driver
+stubs to allow userspace to drive the device, such as in case of
+virtualization.
+
+driverctl integrates with udev to support overriding
+driver selection for both cold- and hotplugged devices from the
+moment of discovery, but can also change already assigned drivers,
+assuming they are not in use by the system. The driver overrides
+created by driverctl are persistent across system reboots
+by default.
+
+%prep
+%setup -q -n %{name}-%{version}-%{commit}
+
+%install
+%make_install
+
+%files
+%license COPYING
+%doc README TODO
+%{_sbindir}/driverctl
+%{_udevrulesdir}/*.rules
+%{_udevrulesdir}/../vfio_name
+%dir %{_sysconfdir}/driverctl.d
+%{_datadir}/bash-completion/
+%{_mandir}/man8/driverctl.8*
+
+%post
+%udev_rules_update
+
+%postun
+%udev_rules_update
+
+%changelog
+* Tue Jan 31 2017 Timothy Redaelli <tredaelli@redhat.com> - 0.95-1
+- Update to 0.95
+- update URLs to new group-based location
+
+* Fri Sep 16 2016 Panu Matilainen <pmatilai@redhat.com> - 0.91-1
+- Use a relative path from udevrulesdir
+- Use fedorable source url which spectool actually understands
+- Move bash completions to newer standard in %%{_datadir}/bash-completion
+- Use %%make_install macro
+- Require /usr/sbin/udevadm for %%post and %%postun
+
+* Fri Sep 2 2016 Panu Matilainen <pmatilai@redhat.com> - 0.74-1
+- Initial package