All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] kodi: fix build when BR2_PACKAGE_LIBFSLVPUWRAP=y
Date: Thu, 9 Jun 2016 23:38:16 +0200	[thread overview]
Message-ID: <20160609233816.1a494a7a@free-electrons.com> (raw)
In-Reply-To: <20160609211911.GC3826@free.fr>

Hello,

On Thu, 9 Jun 2016 23:19:11 +0200, Yann E. MORIN wrote:

> > This is a known bug in Kodi, which nobody has investigated so far.  
> 
> Saying that "nobody has investigated" is wrong. Both Bernd and I have
> done some research on the topic [0].

True.

> And we concluded that upstream is unwilling to take patches that will
> accept only .pyc or .pyo to be present. Upstream *wants* to have the .py
> files present. Period.

Another upstream project also rejected the idea of working just
with .pyc files, until I showed the filesystem size difference between
having .py+.pyc and having just .pyc. Have you tried this approach with
the Kodi people?

(Though I admit it might be less impressive than what the case I had,
due to the massive size of Kodi and its dependencies.)

> So indeed, noone has tried to fix it, because the fix has *zero* chance
> of getting upstream.
> 
> I however submitted two proposals that would make it impossible to have
> that situation, but you did not like them (FTR: one was to hide Kodi
> away when .py files were not present, the other was to add options for
> packages to require .py files to be kept).
> 
> So, unless we revise our position, the bug will stay. And it is a
> Buildroot bug, not an upstream one.

It is and remains an upstream bug, there is absolutely no reason to
not work with just .pyc/.pyo files.

However, since there has been apparently no movement on that side
upstream, then let's just add the dependency that you suggested. It's a
crappy solution, but our motto is to follow upstream, so when upstream
is crappy, so we are :)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-06-09 21:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 15:54 [Buildroot] [PATCH 1/1] kodi: fix build when BR2_PACKAGE_LIBFSLVPUWRAP=y Sébastien Szymanski
2016-05-17 20:53 ` Bernd Kuhls
2016-05-18  7:30   ` Sébastien Szymanski
2016-05-18 13:04     ` Sébastien Szymanski
2016-06-09 20:42 ` Thomas Petazzoni
2016-06-09 21:19   ` Yann E. MORIN
2016-06-09 21:38     ` Thomas Petazzoni [this message]
2016-06-09 21:48       ` Yann E. MORIN
2016-06-09 21:50         ` Thomas Petazzoni
2016-06-09 22:00           ` Yann E. MORIN

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=20160609233816.1a494a7a@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 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.