Bugzilla Bug 153727

# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

inherit kde

DESCRIPTION="A NetworkManager front-end for KDE"
HOMEPAGE="http://en.opensuse.org/Projects/KNetworkManager"
LICENSE="GPL-2"
SRC_URI="http://distfiles.evolution-mission.org/kde/${PN}-${PV##*_p}.tar.bz2"
KEYWORDS="~amd64 ~x86"

DEPEND="net-misc/NetworkManager
        >=kde-base/kdelibs-3.2
        || ( >=dev-libs/dbus-qt3-old-0.70 ( =sys-apps/dbus-0.60 or 0.33 ) )
        sys-apps/hal"

S="${WORKDIR}/${PN}-${PV##*_p}"

pkg_setup() {
        kde_pkg_setup

        if "has_version <sys-apps/dbus-0.9*" && ! built_with_use sys-apps/dbus
qt3 ; then
                echo
                eerror "You must rebuild sys-apps/dbus with USE=\"qt3\""
                die "sys-apps/dbus not built with qt3 bindings"
        fi
}

I've packaged it to include the necessary structure for the tarball.

Created an attachment (id=100987) [edit]
KNetworkManager-0.1_p20061029.ebuild

Attached ebuild. Sorry for the posting of the ebuild in the description, was an
accident.

Please use lower case for ebuild names. Feel free to drop by in #gentopia and
commit this to the gentopia overlay.

Don't.

Changing the official package is inammissible, there's a bug (either open or
closed, I'm not sure) to install the needed headers from KDE packages. Now that
networkmanager is in portage, it will make sense to do that.

(In reply to comment #3)
> Don't.
> 
> Changing the official package is inammissible, there's a bug (either open or
> closed, I'm not sure) to install the needed headers from KDE packages. Now that
> networkmanager is in portage, it will make sense to do that.
> 
Not sure I'm following what you are talking about. If you are referring to me
tarring it: I tarred from svn based on Suse's script for building
KNetworkManager. I didn't build 0.1 because if I Recall correctly, when I tried
to build 0.1 with the same ebuild, it had some sort of issue or something.

I'll restest with 0.1 if you want me to. 

I might have misunderstood but you said "I've packaged it to include the
necessary structure for the tarball.", I supposed you were referring to the
need of some internal headers some time ago.

Also, what was the issue with 0.1? Does not seem wise to add just a random svn
snapshot, if 0.1 is broken just tell so to the authors and wait for a 0.2
release.

Created an attachment (id=100998) [edit]
knetworkmanager-0.1.ebuild

Added 0.1 ebuild per request of flameeyes. In order to get it to work I had to
export a variable for unsermake, if that's not the proper way, I'll gladly fix
it.

Created an attachment (id=101000) [edit]
knetworkmanager-0.1_p20061029.ebuild

Fixed up the ebuild's deps for networkmanager, and renamed to lowercase.

> Fixed up the ebuild's deps for networkmanager, and renamed to lowercase.
Fetching the source does not work any longer, as it tries to fetch
knetworkmanager-20061029.tar.bz2 instead of KNetworkManager-20061029.tar.bz2
Same problem holds for variable S.
Possible solution: Replace ${PN} by "KNetworkManager" in both cases.

Another problem: There is a dependency to net-misc/networkmanager, but the
portage tree contains only net-misc/NetworkManager. Either fix the
KNetworkManager ebuild or rename package NetworkManager to networkmanager.

I'll fix the source that's no problem. The dep on networkmanager is because
NetworkManager is going to be renamed from what I've been told to lowercase.

If it's code is anything like kpowersave... it should be banned.

( http://mail.kde.org/pipermail/kde-networkmanager/2007-July/000195.html )

KNetworkmanager 0.2 was released recently, so I have to wonder if this can get
included in the official tree.

kde-misc/knetworkmanager-0.2 is in the tree now.
Please test and wave back if doesn't work.

*** This bug has been marked as a duplicate of bug 135331 ***