Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/openjpeg: bump to version 2.1
Date: Mon, 25 Apr 2016 21:29:20 +0200	[thread overview]
Message-ID: <87potdo5bj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1461597623-14629-2-git-send-email-angelo.compagnucci@gmail.com> (Angelo Compagnucci's message of "Mon, 25 Apr 2016 17:20:22 +0200")

>>>>> "Angelo" == Angelo Compagnucci <angelo.compagnucci@gmail.com> writes:

 > This patch bumps openjpeg to version 2.1 and converts the
 > package to use cmake.

 > Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>

A bit more detailed changelog would be good, E.G. the fact that it has
now moved to github. What happened to all those optional dependencies?

Looking at the 2.x release notes I see it mentions various API
changes. Have you verified that the reverse dependencies
(efl, gst1-plugins-bad, poppler) still build/work with the new version?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2016-04-25 19:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 15:20 [Buildroot] [PATCH 0/2] python-pillow: new package Angelo Compagnucci
2016-04-25 15:20 ` [Buildroot] [PATCH 1/2] package/openjpeg: bump to version 2.1 Angelo Compagnucci
2016-04-25 19:28   ` Thomas Petazzoni
2016-04-25 20:05     ` Angelo Compagnucci
2016-04-25 20:14       ` Thomas Petazzoni
2016-04-25 20:18       ` Samuel Martin
2016-04-25 20:43         ` Angelo Compagnucci
2016-04-25 20:53           ` Angelo Compagnucci
2016-04-25 20:56           ` Samuel Martin
2016-04-25 21:01             ` Angelo Compagnucci
2016-04-25 19:29   ` Peter Korsgaard [this message]
2016-04-25 20:06     ` Angelo Compagnucci
2016-04-25 21:19       ` Angelo Compagnucci
2016-04-25 15:20 ` [Buildroot] [PATCH 2/2] package/python-pillow: new package Angelo Compagnucci
2016-04-25 20:35   ` Thomas Petazzoni
2016-04-25 20:49     ` Angelo Compagnucci

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=87potdo5bj.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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