Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 05/22] Update libnotify to version 0.7.6
Date: Mon, 22 Jun 2015 15:34:39 +0300	[thread overview]
Message-ID: <558800DF.60005@linux.intel.com> (raw)
In-Reply-To: <CALbNGRTj_Z-UqkrAXVCXqpKUgpYX+mewKFe6kgdeV0+XY60-Og@mail.gmail.com>

On 06/20/2015 12:41 AM, Andreas Müller wrote:

> Emotional part: I am sorry for my last email's style and I hope this
> does not cause lack of motivation on your side. This was definitely
> not an email that should have gone out this way.

Thank you Andreas, I very much appreciate you saying this. Also my email 
had the wrong tone, a bit too blunt and provocative perhaps.

> Technical part: Although your patches break things I think _now_ that
> they point in the right direction. The old gnome stuff turns into a
> maintenance burden with every new tool/library introduced. As Martin
> pointed out: I have tried to update libnotify two years ago and
> stopped due to huge fallout.
> Now we expect same but the situation is different: We have stable
> releases of better quality than two years ago. If still interested in
> gnome 2 style user experience and not accepting gnome 3 one could work
> with releases (or implement/use alternatives Mate/Xfce..).

I have looked at recent commit history for meta-gnome; my impression is 
that it only gets ad-hoc patching so that things still compile, and 
nobody is doing a systematic effort to keep things up to date and 
working. So the layer is effectively unmaintained and slowly bit rots.

> One note regarding gnome 3: I played around with gnome 3 long time ago
> but stopped messing around with gobject-introspection which looked
> mandatory for some packages. I think if we want to migrate meta-gnome
> to gnome 3 we should think of migrating meta-gir to meta-gnome.

Yes; getting gobject-introspection to work and perhaps taking it into 
oe-core is something that we'd really like to do, so I plan to look at 
it when I have a bit of breathing space later this or next week.


Regards,
Alex


  reply	other threads:[~2015-06-22 12:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 13:19 [PATCH 00/22] Update webkitgtk to latest stable upstream; replace midori with epiphany Alexander Kanavin
2015-06-17 13:19 ` [PATCH 01/22] Change tarball compression to xz for gnome recipes Alexander Kanavin
2015-06-17 13:19 ` [PATCH 02/22] Enable icu feature in harfbuzz recipe Alexander Kanavin
2015-06-17 13:19 ` [PATCH 03/22] Add arch conversion routine to cmake.bbclass Alexander Kanavin
2015-06-17 13:19 ` [PATCH 04/22] Update jpeg recipe to version 9a Alexander Kanavin
2015-06-17 13:19 ` [PATCH 05/22] Update libnotify to version 0.7.6 Alexander Kanavin
2015-06-17 14:59   ` Jussi Kukkonen
2015-06-18 11:23     ` Alexander Kanavin
2015-06-18 12:35       ` Andreas Müller
2015-06-18 13:02         ` Martin Jansa
2015-06-18 13:16         ` Alexander Kanavin
2015-06-18 14:42           ` Andreas Müller
2015-06-19 21:41             ` Andreas Müller
2015-06-22 12:34               ` Alexander Kanavin [this message]
     [not found]   ` <CALbNGRS5T12OGFK-C9B4DSyWsz-nRe8zsm=8_xnv4xtqhBHUXg@mail.gmail.com>
2015-06-17 15:01     ` Andreas Müller
2015-06-17 13:19 ` [PATCH 06/22] Add a recipe for giflib Alexander Kanavin
2015-06-17 13:19 ` [PATCH 07/22] Add a recipe for libyaml Alexander Kanavin
2015-06-17 13:19 ` [PATCH 08/22] Add a recipe for ruby Alexander Kanavin
2015-06-17 13:19 ` [PATCH 09/22] Add a recipe for libsecret Alexander Kanavin
2015-06-17 15:05   ` Andreas Müller
2015-06-17 18:54     ` akuster808
2015-06-18 11:54       ` Alexander Kanavin
2015-06-18 11:31     ` Alexander Kanavin
2015-06-17 13:19 ` [PATCH 10/22] Add a recipe for libwebp Alexander Kanavin
2015-06-17 13:19 ` [PATCH 11/22] Add a recipe for webkitgtk 2.8.3 Alexander Kanavin
2015-06-17 13:19 ` [PATCH 12/22] Add a recipe for p11-kit Alexander Kanavin
2015-06-17 13:19 ` [PATCH 13/22] Add a recipe for gcr Alexander Kanavin
2015-06-17 13:19 ` [PATCH 14/22] Add a recipe for iso-codes Alexander Kanavin
2015-06-17 13:19 ` [PATCH 15/22] Add a recipe for libwnck3 Alexander Kanavin
2015-06-17 13:19 ` [PATCH 16/22] Add a recipe for gnome-desktop3 Alexander Kanavin
2015-06-17 13:19 ` [PATCH 17/22] Add a warning suppression patch to glib Alexander Kanavin
2015-06-17 13:19 ` [PATCH 18/22] Add a recipe gsettings-desktop-schemas Alexander Kanavin
2015-06-17 13:19 ` [PATCH 19/22] Add a recipe for epiphany Alexander Kanavin
2015-06-17 13:19 ` [PATCH 20/22] Remove the recipe for the obsolete webkit-gtk 1.8.3 Alexander Kanavin
2015-06-17 13:19 ` [PATCH 21/22] Remove the midori recipe and replace references to midori with epiphany Alexander Kanavin
2015-06-17 13:19 ` [PATCH 22/22] poky: update distro files related to webkitgtk update and epiphany addition Alexander Kanavin
2015-06-17 16:01 ` [PATCH 00/22] Update webkitgtk to latest stable upstream; replace midori with epiphany Paul Eggleton
2015-06-18 11:46   ` Alexander Kanavin

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=558800DF.60005@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=schnitzeltony@googlemail.com \
    /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