From: Max Krummenacher <max.oss.09@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: morty branch XFCE no longer builds, missing libwnck3
Date: Mon, 02 Jan 2017 12:11:43 +0100 [thread overview]
Message-ID: <1483355503.2262.6.camel@gmail.com> (raw)
In-Reply-To: <45e5bbb8-6e17-d030-cf2c-f54e2c2e30ba@topic.nl>
Hi
Am Montag, den 02.01.2017, 09:18 +0100 schrieb Mike Looijmans:
> There's no trace of any attempt to bring back 'libwnck3' in the morty branch,
> am I the only one in the world using morty to build an XCFE image?
You are not the only one.
As there was already talk on the mailing lists to either revert the removal
on oe-core or merge the relevant morty-next commit in meta-openembedded I
put the recipes into my own layer to keep my stuff building.
It would probably be beneficial for future recipe moves to first add stuff
to the destination layer before removing it from the source, particularly on
the non master branches.
Max
next prev parent reply other threads:[~2017-01-02 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 9:54 morty branch XFCE no longer builds, missing libwnck3 Mike Looijmans
2016-12-20 11:53 ` Andreas Müller
2016-12-21 1:33 ` akuster808
2017-01-02 8:18 ` Mike Looijmans
2017-01-02 11:11 ` Max Krummenacher [this message]
2017-01-02 17:07 ` akuster808
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=1483355503.2262.6.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.