Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Make libmicrohttpd version configurable
Date: Tue, 6 Mar 2012 18:49:33 +0100	[thread overview]
Message-ID: <20120306184933.5dbaf329@skate> (raw)
In-Reply-To: <CAG0mjpva6VP1u7EK9oOXUqeYYypCiC2yuE7ag4UtBqCkgc52UA@mail.gmail.com>

Hello Roland,

Please don't reply just to me: keep the list in Cc.

Le Tue, 6 Mar 2012 19:38:39 +0200,
Roland Uuesoo <rolandu@gmail.com> a ?crit :

> Version 0.4.6 is 2 years old (13 march 2010).
> 
> A lot of bugs/security problems have been fixed.
> 
> And there are new features added.

Ok.

> Made it configurable because someone might need the old version.

Then just bump the version to whatever more recent version is
available. We don't support multiple versions per package in Buildroot,
because it would be a maintenance nightmare. For example: each version
will need different patches, different configuration options, etc.

So we have decided to keep things simple and support only one version
at a time, except for U-Boot, Barebox, kernel, and critical things like
that. People doing a project with Buildroot are anyway forking a
particular version of Buildroot to ensure that they are fixed on a
given version of all the components they are using in their system.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-03-06 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 17:18 [Buildroot] [PATCH] Make libmicrohttpd version configurable rolandu at gmail.com
2012-03-06 17:20 ` Thomas Petazzoni
     [not found]   ` <CAG0mjpva6VP1u7EK9oOXUqeYYypCiC2yuE7ag4UtBqCkgc52UA@mail.gmail.com>
2012-03-06 17:49     ` Thomas Petazzoni [this message]
2012-03-06 18:14       ` Roland

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=20120306184933.5dbaf329@skate \
    --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