From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: yegorslists@googlemail.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/python-m2crypto: remove package
Date: Mon, 16 Dec 2024 10:14:34 +0200 [thread overview]
Message-ID: <87o71cvyc5.fsf@tarshish> (raw)
In-Reply-To: <20241216081158.250767-1-yegorslists@googlemail.com> (yegorslists@googlemail.com's message of "Mon, 16 Dec 2024 09:11:58 +0100")
Hi Yegor,
On Mon, Dec 16 2024, yegorslists@googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> The python-m2crypto package was removed as it is in maintained
> only mode and is not recommended for new projects.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> Config.in.legacy | 7 +++++++
> package/Config.in | 1 -
> package/python-m2crypto/Config.in | 9 ---------
> package/python-m2crypto/python-m2crypto.hash | 5 -----
> package/python-m2crypto/python-m2crypto.mk | 18 ------------------
> 5 files changed, 7 insertions(+), 33 deletions(-)
> delete mode 100644 package/python-m2crypto/Config.in
> delete mode 100644 package/python-m2crypto/python-m2crypto.hash
> delete mode 100644 package/python-m2crypto/python-m2crypto.mk
DEVELOPERS should also be updated.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-16 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 8:11 [Buildroot] [PATCH] package/python-m2crypto: remove package yegorslists
2024-12-16 8:14 ` Baruch Siach via buildroot [this message]
2024-12-16 10:24 ` Yegor Yefremov
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=87o71cvyc5.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=yegorslists@googlemail.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 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.