From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/sdl_mixer: disable libmad support for static build only
Date: Sun, 21 Feb 2016 21:44:03 +0100 [thread overview]
Message-ID: <20160221214403.217426b2@free-electrons.com> (raw)
In-Reply-To: <CABLs7GVft7bo9tdj8wMh4E0Z9DNQssZNWw4XYo9V=ANBdpceOg@mail.gmail.com>
Dear Rodrigo Rebello,
On Sun, 21 Feb 2016 17:37:28 -0300, Rodrigo Rebello wrote:
> That's a good point. Well, at least chocolate-doom is being actively
> maintained, so we'll be able to upstream a patch in that case.
>
> As for the other 3, do you think keeping patches for them in buildroot
> could turn out to be a hassle in the long run?
Having patches that are not upstream is a hassle in general.
But since those packages are basically unmaintained upstream as far as
I remember, it means upstream won't do any new release, and therefore
we won't have to update/change the patches. Having patches is really a
big annoyance when the upstream project is still active and makes
releases, since we have to update our patches whenever we bump the
package.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-21 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 16:55 [Buildroot] [PATCH] package/sdl_mixer: disable libmad support for static build only Romain Naour
2016-02-21 17:18 ` Thomas Petazzoni
2016-02-21 20:06 ` Rodrigo Rebello
2016-02-21 20:13 ` Thomas Petazzoni
2016-02-21 20:37 ` Rodrigo Rebello
2016-02-21 20:44 ` Thomas Petazzoni [this message]
2016-03-02 20:48 ` Romain Naour
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=20160221214403.217426b2@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.