From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 13/13] microperl: mark as DEPRECATED
Date: Thu, 20 Sep 2012 22:22:03 +0200 [thread overview]
Message-ID: <20120920222203.2c608fcf@skate> (raw)
In-Reply-To: <1347107325-4163-13-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Sat, 8 Sep 2012 14:28:45 +0200, Francois Perrad wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/microperl/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/microperl/Config.in b/package/microperl/Config.in
> index 66bbedd..19d104a 100644
> --- a/package/microperl/Config.in
> +++ b/package/microperl/Config.in
> @@ -2,6 +2,7 @@ config BR2_PACKAGE_MICROPERL
> bool "microperl"
> # needs fork()
> depends on BR2_USE_MMU
> + depends on BR2_DEPRECATED
If microperl is deprecated, is it really useful to have patches 7, 8,
9, 10, 11 and 12 that are making improvements to it, and updating it to
a more recent version?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-20 20:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 12:28 [Buildroot] [PATCH 01/13] perl: new package v6 Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 02/13] perl: add an option for miniperl Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 03/13] perl: add DB_File Francois Perrad
2012-09-20 19:57 ` Thomas Petazzoni
2012-09-21 18:26 ` François Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 04/13] gdbm: new package Francois Perrad
2012-09-12 5:30 ` Arnout Vandecappelle
2012-09-08 12:28 ` [Buildroot] [PATCH 05/13] perl: add GDBM_File Francois Perrad
2012-09-20 19:59 ` Thomas Petazzoni
2012-09-21 18:36 ` François Perrad
2012-09-21 19:01 ` Thomas Petazzoni
2012-09-24 8:43 ` Arnout Vandecappelle
2012-09-08 12:28 ` [Buildroot] [PATCH 06/13] cpanminus: new package v3 Francois Perrad
2012-09-20 20:04 ` Thomas Petazzoni
2012-09-20 21:35 ` Arnout Vandecappelle
2012-09-21 18:25 ` François Perrad
2012-09-21 19:02 ` Thomas Petazzoni
2012-09-08 12:28 ` [Buildroot] [PATCH 07/13] microperl: build extensions at build time Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 08/13] microperl: bump version to 5.14.2 Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 09/13] microperl: improve configure step on 64bits platform Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 10/13] microperl: install more modules by default Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 11/13] microperl: bump version to 5.16.1 Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 12/13] microperl: remove host-microperl Francois Perrad
2012-09-08 12:28 ` [Buildroot] [PATCH 13/13] microperl: mark as DEPRECATED Francois Perrad
2012-09-20 20:22 ` Thomas Petazzoni [this message]
2012-09-21 18:53 ` François Perrad
2012-09-21 18:59 ` Thomas Petazzoni
2012-09-23 15:11 ` François Perrad
2012-09-23 15:25 ` Thomas Petazzoni
2012-09-20 19:56 ` [Buildroot] [PATCH 01/13] perl: new package v6 Thomas Petazzoni
2012-09-21 21:29 ` [Buildroot] [UNSURE]Re: " François Perrad
2012-09-22 3:38 ` Thomas Petazzoni
2012-09-24 20:20 ` [Buildroot] " Arnout Vandecappelle
2012-09-25 17:17 ` [Buildroot] [UNSURE]Re: " François Perrad
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=20120920222203.2c608fcf@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