All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 09/23] evolution-data-server: upgrade 3.34.1 -> 3.34.2
Date: Sat, 28 Dec 2019 10:35:37 -0800	[thread overview]
Message-ID: <CAMKF1soU+iahbZASB1kxvF1f=8e7FSDfHVP+geeM5fg5TjchjQ@mail.gmail.com> (raw)
In-Reply-To: <CALbNGRR7mdJT8fbnB5AONcRtPmxVn_v+bw7Jz6S-aKfPsO6D3g@mail.gmail.com>

On Sat, Dec 28, 2019 at 3:29 AM Andreas Müller <schnitzeltony@gmail.com> wrote:
>
> On Sat, Dec 28, 2019 at 4:22 AM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Fri, Dec 27, 2019 at 3:48 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
> > >
> > > On Sat, Dec 28, 2019 at 12:19 AM Khem Raj <raj.khem@gmail.com> wrote:
> > > > I think version specific information should be in bb file not inc
> > > we have a native build and it just builds some tools required. Both
> > > native/target share same version which is set in
> > > evolution-data-server.inc. So maybe I missed something but what kind
> > > of change do you suggest?
> > >
> >
> > hmm if it shares with native/nativesdk that might be fine
> > why dont we use bbclassextend for the native version ?
> >
> * Native and target recipes do not share much in common (see
> evolution-data-server.inc): As said: Native recipe just builds few
> necessary tools with a set of dependencies reduced to minimum.
> * Most pieces would require a specific entry
> (DEPENDS/do_configure/do_compile/do_install/RDEPENDS) for native and
> target. Since target recipe is already more complex than most recipes,
> extending to native would confuse more and cause recipe less readable.
> * There is no nativesdk yet. If someone needs it: extending target
> recipe should do.
> * This discussion is unrelated to this patch - right?
>

yes

> Andreas


  reply	other threads:[~2019-12-28 18:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 21:30 [PATCH 01/23] exo: upgrade 0.12.10 -> 0.12.11 Andreas Müller
2019-12-27 21:30 ` [PATCH 02/23] tumbler: upgrade 0.2.7 -> 0.2.8 Andreas Müller
2019-12-27 21:31 ` [PATCH 03/23] catfish: upgrade 1.4.10 -> 1.4.11 Andreas Müller
2019-12-27 21:31 ` [PATCH 04/23] cppunit: upgrade 1.14.0 -> 1.15.1 Andreas Müller
2019-12-27 21:31 ` [PATCH 05/23] xfce4-terminal: upgrade 0.8.8 -> 0.8.9 Andreas Müller
2019-12-27 21:31 ` [PATCH 06/23] gnome-calculator: initial add 3.34.1 Andreas Müller
2019-12-27 21:31 ` [PATCH 07/23] evince: upgrade 3.34.1 -> 3.34.1 Andreas Müller
2019-12-27 21:31 ` [PATCH 08/23] file-roller: upgrade 3.32.2 -> 3.32.3 Andreas Müller
2019-12-27 21:31 ` [PATCH 09/23] evolution-data-server: upgrade 3.34.1 -> 3.34.2 Andreas Müller
2019-12-27 23:19   ` Khem Raj
2019-12-27 23:48     ` Andreas Müller
2019-12-28  3:22       ` Khem Raj
2019-12-28 11:29         ` Andreas Müller
2019-12-28 18:35           ` Khem Raj [this message]
2019-12-27 21:31 ` [PATCH 10/23] gedit: upgrade 3.34.0 -> 3.34.1 Andreas Müller
2019-12-27 21:31 ` [PATCH 11/23] gnome-autoar: upgrade 0.2.3 -> 0.2.4 Andreas Müller
2019-12-27 21:31 ` [PATCH 12/23] gnome-control-center: upgrade 3.34.1 -> 3.34.2 Andreas Müller
2019-12-27 21:31 ` [PATCH 13/23] gnome-desktop3: " Andreas Müller
2019-12-27 21:31 ` [PATCH 14/23] gnome-flashback: " Andreas Müller
2019-12-27 21:31 ` [PATCH 15/23] gnome-session: " Andreas Müller
2019-12-27 21:31 ` [PATCH 16/23] gnome-settings-daemon: upgrade " Andreas Müller
2019-12-27 21:31 ` [PATCH 17/23] gnome-shell-extensions: " Andreas Müller
2019-12-27 21:31 ` [PATCH 18/23] gnome-shell: " Andreas Müller
2019-12-27 21:31 ` [PATCH 19/23] gvfs: upgrade 1.42.1 -> 1.42.2 Andreas Müller
2019-12-27 21:31 ` [PATCH 20/23] libgdata: upgrade 0.17.10 -> 0.17.11 Andreas Müller
2019-12-27 21:31 ` [PATCH 21/23] mutter: upgrade 3.34.1 -> 3.34.2 Andreas Müller
2019-12-27 21:31 ` [PATCH 22/23] nautilus: " Andreas Müller
2019-12-27 21:31 ` [PATCH 23/23] yelp-xsl: upgrade 3.34.0 " Andreas Müller

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='CAMKF1soU+iahbZASB1kxvF1f=8e7FSDfHVP+geeM5fg5TjchjQ@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=schnitzeltony@gmail.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 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.