From: Phil Blundell <pb@pbcl.net>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/5] connman: Add VPN support
Date: Mon, 13 May 2013 16:20:47 +0100 [thread overview]
Message-ID: <1368458447.6920.30.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1368449357-3191-2-git-send-email-jukka.rissanen@linux.intel.com>
On Mon, 2013-05-13 at 15:49 +0300, Jukka Rissanen wrote:
> +do_install_append_${PN}-vpn() {
> + mkdir -p ${D}${libdir}/connman/scripts
> + mkdir -p ${D}${libdir}/connman/plugins-vpn
> +}
> +
Does that actually do anything useful?
>+bb.note( "Adding rdependency on %s to %s" % ( rdepends, package ) )
I know the existing connman.inc does the same thing, but I don't think
we want to proliferate this sort of debugging chit-chat in new code.
Also, the way that this code (both the existing stuff and the new block
you've added) interacts with do_split_packages() is a bit hokey. You
have a hook function which basically just adds an entry to a list, and
then a separate loop which iterates over the resulting list and fiddles
with the RDEPENDS. As far as I can tell there's no reason that the
RDEPENDS tinkering couldn't be done inside the hook function itself,
which would avoid having two copies of essentially the same code.
> -FILES_${PN} = "${bindir}/* ${sbindir}/* ${libexecdir}/* ${libdir}/lib*.so.* \
> +FILES_${PN} = "${sbindir}/connmand ${libexecdir}/* ${libdir}/lib*.so.* \
> ${libdir}/connman/plugins \
> - ${sysconfdir} ${sharedstatedir} ${localstatedir} \
> - ${base_bindir}/* ${base_sbindir}/* ${base_libdir}/*.so* ${datadir}/${PN} \
> - ${datadir}/dbus-1/system-services/*"
> + ${sysconfdir}/connman ${sysconfdir}/dbus-1/system.d/connman.conf \
> + @base_contains('DISTRO_FEATURES','sysvinit','${sysconfdir}/init.d','',d)} \
> + ${sharedstatedir} ${localstatedir} \
> + ${base_bindir}/* ${base_sbindir}/* ${base_libdir}/*.so* \
> + ${datadir}/${PN}"
That seems like rather a wide-ranging set of changes. You prepended
${PN}-vpn to PACKAGES which should mean that it gets first pick of the
FILES. Are all those changes to FILES_${PN} actually necessary?
p.
next prev parent reply other threads:[~2013-05-13 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 12:49 [PATCH v2 0/5] Enable VPN support in ConnMan Jukka Rissanen
2013-05-13 12:49 ` [PATCH v2 1/5] connman: Add VPN support Jukka Rissanen
2013-05-13 15:20 ` Phil Blundell [this message]
2013-05-13 12:49 ` [PATCH v2 2/5] connman: Add OpenVPN support Jukka Rissanen
2013-05-13 12:49 ` [PATCH v2 3/5] connman: Add vpnc support Jukka Rissanen
2013-05-13 12:49 ` [PATCH v2 4/5] connman: Add L2TP support Jukka Rissanen
2013-05-13 12:49 ` [PATCH v2 5/5] connman: Add PPTP support Jukka Rissanen
2013-05-13 13:39 ` [PATCH v2 0/5] Enable VPN support in ConnMan Martin Jansa
2013-05-13 13:55 ` Jukka Rissanen
2013-05-13 14:04 ` Phil Blundell
2013-05-13 14:42 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1368458447.6920.30.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=jukka.rissanen@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox