Hello community,

here is the log from the commit of package driverctl for openSUSE:Factory 
checked in at 2018-03-11 15:24:24
Comparing /work/SRC/openSUSE:Factory/driverctl (Old)
 and      /work/SRC/openSUSE:Factory/.driverctl.new (New)

Package is "driverctl"

Sun Mar 11 15:24:24 2018 rev:1 rq:584647 version:0.95

New Changes file:

--- /dev/null   2018-03-01 08:56:54.644963210 +0100
+++ /work/SRC/openSUSE:Factory/.driverctl.new/driverctl.changes 2018-03-11 
15:24:24.921014604 +0100
@@ -0,0 +1,10 @@
+Fri Mar  9 10:39:29 CET 2018 - n...@suse.de
+- use pkgconfig as it allows OBS to pick packages optimized for building.
+Wed Mar  7 16:26:24 CET 2018 - n...@suse.de
+- Initial package (version:0.95)



Other differences:
++++++ driverctl.spec ++++++
# spec file for package driverctl
# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/

%global commit  3c668744f2242e453fdcd6dca36d3e1d82d0367a
Name:           driverctl
Version:        0.95
Release:        0
Summary:        Device driver control utility
License:        LGPL-2.0-only
Group:          System/Management
URL:            https://gitlab.com/driverctl/driverctl
Source0:        archive.tar.gz

BuildRequires:  pkgconfig(systemd)
Requires:       coreutils
Requires:       udev
BuildArch:      noarch

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

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.

%setup -q -n %{name}-%{version}-%{commit}



%license COPYING
%dir %{_sysconfdir}/driverctl.d




Reply via email to