From: Martin Jansa <martin.jansa@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] x11vnc: move recipe to meta-oe
Date: Fri, 16 Oct 2015 16:44:08 +0200 [thread overview]
Message-ID: <20151016144408.GB2544@jama> (raw)
In-Reply-To: <56210C4A.2090400@mlbassoc.com>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Fri, Oct 16, 2015 at 08:40:10AM -0600, Gary Thomas wrote:
> On 2015-10-16 08:25, Ioan-Adrian Ratiu wrote:
> > x11vnc can be configured with --use-system-libvncserver to use an
> > external libvncserver which will be added to meta-oe. Since oe-core
> > should not depend on meta-oe, we move x11vnc there.
> >
> > Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
>
> Just curious why not the other way - move libvncserver to OE-core?
> x11vnc seems like one of the very few [and useful] X based tools that
> are present in OE-core that it seems like a huge step backwards to
> move it out.
It was discussed in "[OE-core] [oe] [meta-oe][PATCH v2] meta-oe:
recipes-graphics: add libvncserver recipe" thread and I agree with
Otavio that x11vnc doesn't look so fundamental component used by most
embedded builds to deserver being in the core.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-10-16 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 14:25 [PATCH] x11vnc: move recipe to meta-oe Ioan-Adrian Ratiu
2015-10-16 14:40 ` Gary Thomas
2015-10-16 14:44 ` Martin Jansa [this message]
2015-10-16 15:21 ` Gary Thomas
2015-10-16 15:29 ` Otavio Salvador
2015-10-16 15:41 ` Gary Thomas
2015-10-16 15:48 ` Otavio Salvador
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=20151016144408.GB2544@jama \
--to=martin.jansa@gmail.com \
--cc=gary@mlbassoc.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