From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/mcrypt: drop package
Date: Thu, 19 Aug 2021 23:05:39 +0200 [thread overview]
Message-ID: <20210819230539.16ac5e4f@windsurf> (raw)
In-Reply-To: <20210805174252.2661314-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
On Thu, 5 Aug 2021 19:42:51 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Drop mcrypt which is not maintained anymore (no release since 2008).
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Config.in.legacy | 7 ++
> package/Config.in | 1 -
> package/mcrypt/0001-CVE-2012-4409.patch | 25 -------
> package/mcrypt/0002-CVE-2012-4426.patch | 35 ---------
> package/mcrypt/0003-CVE-2012-4527.patch | 99 -------------------------
> package/mcrypt/0004-no-rpath.patch | 17 -----
> package/mcrypt/Config.in | 12 ---
> package/mcrypt/mcrypt.hash | 3 -
> package/mcrypt/mcrypt.mk | 24 ------
> 9 files changed, 7 insertions(+), 216 deletions(-)
> delete mode 100644 package/mcrypt/0001-CVE-2012-4409.patch
> delete mode 100644 package/mcrypt/0002-CVE-2012-4426.patch
> delete mode 100644 package/mcrypt/0003-CVE-2012-4527.patch
> delete mode 100644 package/mcrypt/0004-no-rpath.patch
> delete mode 100644 package/mcrypt/Config.in
> delete mode 100644 package/mcrypt/mcrypt.hash
> delete mode 100644 package/mcrypt/mcrypt.mk
Do we have a good reason to drop these packages? We have lots of
packages with no upstream activity, and we drop them only when there is
some particular issue. What prompted you to propose these packages for
removal ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-19 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 17:42 [Buildroot] [PATCH 1/2] package/mcrypt: drop package Fabrice Fontaine
2021-08-05 17:42 ` [Buildroot] [PATCH 2/2] package/libmcrypt: " Fabrice Fontaine
2021-08-19 21:05 ` Thomas Petazzoni [this message]
2021-08-19 21:21 ` [Buildroot] [PATCH 1/2] package/mcrypt: " Fabrice Fontaine
2021-08-19 21:58 ` 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=20210819230539.16ac5e4f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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