From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/kodi: Move all kodi packages to subdirectories of package/kodi/
Date: Sun, 14 Jun 2015 11:22:49 +0200 [thread overview]
Message-ID: <20150614112249.5edc2e52@free-electrons.com> (raw)
In-Reply-To: <1434273033-31723-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sun, 14 Jun 2015 11:10:30 +0200, Bernd Kuhls wrote:
> Kodi 15.0 Isengard will contain new support for binary addons.
> To prevent adding all those new packages to the root level of package/
> introduce a new main hierarchy starting from package/kodi/.
>
> This patch moves the current Kodi 14.2 Helix packages to this new
> directory in preparation for the upcoming version bump.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
We went exactly the other way around recently with moving up all the
matchbox packages back to package/ directory.
So, why would we want to do the opposite for Kodi ?
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-06-14 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 9:10 [Buildroot] [PATCH 1/4] package/kodi: Move all kodi packages to subdirectories of package/kodi/ Bernd Kuhls
2015-06-14 9:10 ` [Buildroot] [PATCH 2/4] package/kodi: Move all kodi packages to subdirectories of package/kodi/, part II Bernd Kuhls
2015-06-14 9:10 ` [Buildroot] [PATCH 3/4] package/kodi/kodi: Fix egl/gles compilation with mesa3d and disabled X.org Bernd Kuhls
2015-06-28 14:39 ` Yann E. MORIN
2015-06-14 9:10 ` [Buildroot] [PATCH 4/4] package/kodi/kodi: Remove hyperflous option --disable-dvdcss Bernd Kuhls
2015-06-28 12:49 ` Yann E. MORIN
2015-06-14 9:22 ` Thomas Petazzoni [this message]
2015-06-14 10:28 ` [Buildroot] [PATCH 1/4] package/kodi: Move all kodi packages to subdirectories of package/kodi/ Bernd Kuhls
2015-06-14 10:33 ` Bernd Kuhls
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=20150614112249.5edc2e52@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