From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] package/efl/libevas: Switch to giflib
Date: Sun, 8 Mar 2015 08:46:36 +0100 [thread overview]
Message-ID: <20150308084636.06f56bb6@free-electrons.com> (raw)
In-Reply-To: <CAHkwnC9VfqeHc8SGqwJJu777npQ7brMi=B=Ck6rv6CQUyTHB2Q@mail.gmail.com>
Dear Fabio Porcedda,
On Sun, 8 Mar 2015 08:28:44 +0100, Fabio Porcedda wrote:
> I understand that is a legacy repository but because you talked about
> to send a patch upstream i was trying to understand if there is any
> chance that the patch will be accepted.
>
> So when you have talked about to send the patch upstream didn't know
> about the legacy status of this repository?
Well, when you want to send a patch upstream, then obviously you have
to send the patch based on the latest upstream version. Which generally
involves bumping the Buildroot package to use the latest stable version
from upstream.
In the case of EFL, it indeed involves quite a bit of work, because all
the libraries that used to be split in separate tarballs are now
provided as one single tarball by upstream.
See https://phab.enlightenment.org/phame/live/3/post/efl_1_8/ :
"""
We have merged Ecore, Edje, Eet, Eeze, Efreet, Eina, Eio, Embryo,
Emotion, Ethumb, Evas and Evil into a single EFL package (as you can
see above these are no longer there, but inside the EFL distribution).
We also added in Eldbus, EPhysics, and Escape.
"""
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-08 7:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 19:24 [Buildroot] [PATCH 1/5] package/giflib: New package Bernd Kuhls
2015-01-26 19:24 ` [Buildroot] [PATCH 2/5] package/fbv: Switch to giflib Bernd Kuhls
2015-01-27 15:17 ` Peter Korsgaard
2015-01-29 18:56 ` Bernd Kuhls
2015-01-26 19:24 ` [Buildroot] [PATCH 3/5] package/imlib2: " Bernd Kuhls
2015-01-27 15:25 ` Peter Korsgaard
2015-01-29 19:13 ` Bernd Kuhls
2015-03-07 18:09 ` Fabio Porcedda
2015-01-26 19:24 ` [Buildroot] [PATCH 4/5] package/efl/libevas: " Bernd Kuhls
2015-03-07 16:29 ` Fabio Porcedda
2015-03-07 16:32 ` Thomas Petazzoni
2015-03-07 17:01 ` Fabio Porcedda
2015-03-08 7:15 ` Thomas Petazzoni
2015-03-08 7:28 ` Fabio Porcedda
2015-03-08 7:46 ` Thomas Petazzoni [this message]
2015-03-08 7:54 ` Fabio Porcedda
2015-03-08 8:03 ` Thomas Petazzoni
2015-04-04 16:45 ` Thomas Petazzoni
2015-01-26 19:24 ` [Buildroot] [PATCH 5/5] package/libungif: deprecate package Bernd Kuhls
2015-03-07 17:19 ` Fabio Porcedda
2015-04-04 16:46 ` Thomas Petazzoni
2015-04-08 20:33 ` Bernd Kuhls
2015-01-27 15:12 ` [Buildroot] [PATCH 1/5] package/giflib: New package Peter Korsgaard
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=20150308084636.06f56bb6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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