Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] supertuxkart: new package
Date: Wed, 11 May 2016 22:46:14 +0200	[thread overview]
Message-ID: <90ed3ddb-e172-505e-e742-3c22bfe993ee@mind.be> (raw)
In-Reply-To: <CAAEAJfCMp+K-7jvMc+Aa7fHXq2=wOLo33UMy140Dpk=RHbtahw@mail.gmail.com>



On 05/10/16 15:59, Ezequiel Garcia wrote:
> On 9 May 2016 at 20:16, Arnout Vandecappelle <arnout@mind.be> wrote:
> [..]
>>> Why? If the package bundles a glew, why not using it?
>>
>>
>
> As a matter of fact, they bunde jpeglib, libpng, zlib and a few more as well.

  jpeglib, libpng and zlib are AFAICS only used on Windows and Mac. For us, it's 
using the installed ones. You even added those dependencies :-)

>
>>  We avoid bundled libraries for several reasons:
>>
>
> Sure, I understand why bundling is a shitty idea. My point is:
> it was not OUR idea, but something that comes from upstream.
>
> I haven't checked, but given they bundle their own Irrlicht engine
> (and even they modified it enough to call it Antarctica now), it seems
> they know what they are doing.
>
> Or another possible explanation is that they are lazy, and wanted
> to bundle to make installation easier (in some non-Linux OS?).
>
> Whatever the reasons, I don't want to spend time modifying a package
> in a way that won't be accepted upstream.
>
> [..]
>>
>>  However, it's possible that supertuxkart has made project-specific
>> modifications to libglew, in this case unbundling is difficult. I see that
>> at least it is an older version than what we have.
>>
>
> Exactly my point. And even if they haven't made modifications to some of
> the bundled packages, I really don't want to spend time doing a change that
> is not in the upstream roadmap.

  Fair enough, the bundling is probably not bad enough to block this package.

  Perhaps then add a comment in the .mk file, near the dependencies list, that 
it has bundled modified versions of libglew and irrlicht. Actually we don't have 
irrlicht (yet) so for that it doesn't matter much :-)

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-05-11 20:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  5:33 [Buildroot] [PATCH] supertuxkart: new package Ezequiel Garcia
2016-04-12 23:12 ` Arnout Vandecappelle
2016-05-08 17:33   ` Ezequiel Garcia
2016-05-09 23:16     ` Arnout Vandecappelle
2016-05-10 13:59       ` Ezequiel Garcia
2016-05-11 20:46         ` Arnout Vandecappelle [this message]
2016-05-13 15:59   ` Ezequiel Garcia

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=90ed3ddb-e172-505e-e742-3c22bfe993ee@mind.be \
    --to=arnout@mind.be \
    --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