Mandriva does not want to have the NetworkManager back-end in KDE Solid
in the distribution. The problem is that this back-end is part of
kdebase-workspace in main, while networkmanager is in contrib. I have
made a separate, stand-alone package for this back-end which could have
gone in contrib, but KDE team does not even want to accept that because
the source is already included in main (even if uncompiled).

Is this something which could go in PLF?


For reference, I add the SPEC file so you can get an idea about how it
works. Based on this package, we could then later create a package which
contains the KDE GUI for networkmanager
(http://websvn.kde.org/trunk/kdereview/networkmanagement/)



%define snapshot r1052408
%define srcname networkmanager-0.7

Name:           kdebase-workspace-networkmanager
Summary:        KDE Solid back-end for NetworkManager 0.7
Version:        4.4
Release:        %mkrel 0.%{snapshot}.1
Group:          System/Configuration/Networking
License:        GPLv2+
URL:            http://www.kde.org
#svn co
svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase/workspace/solid/networkmanager-0.7
Source0:        %{srcname}.%{snapshot}.tar.xz
# Make it build stand-alone (by Adam Pigg)
Patch0:         networkmanager-0.7-cmake.patch
BuildRequires:  libnm-util-devel
BuildRequires:  kdebase4-workspace-devel
Requires:       networkmanager
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-buildroot

%description
This Solid module provides support for NetworkManager 0.7.

%prep
%setup -q -n %{srcname}
%patch0 -p1 -b .cmake

%build
%cmake_kde4
%make

%install
rm -rf %{buildroot}
%makeinstall_std -C build

%clean
rm -rf %{buildroot}

%files
%defattr(-,root,root)
%{_datadir}/kde4/services/solidbackends/solid_networkmanager07.desktop
%{_iconsdir}/oxygen/*/apps/networkmanager.png
%{_libdir}/kde4/solid_networkmanager07.so


-- 
Frederik Himpe <[email protected]>


_______________________________________________
PLF-discuss mailing list
[email protected]
https://www.zarb.org/mailman/listinfo/plf-discuss

Reply via email to