From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/e3: new package
Date: Wed, 27 Jul 2022 11:51:13 +0200 [thread overview]
Message-ID: <20220727115113.0d06fb96@windsurf> (raw)
In-Reply-To: <20220213130306.3002130-1-bernd.kuhls@t-online.de>
Hello Bernd,
On Sun, 13 Feb 2022 14:03:06 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/e3/0001-makefile.patch | 42 +++++++++++++++
> .../e3/0002-Align-header-to-avoid-crash.patch | 26 +++++++++
> package/e3/0003-format-1.0.patch | 54 +++++++++++++++++++
> package/e3/0004-e3-gnu-stack.patch | 50 +++++++++++++++++
> package/e3/Config.in | 9 ++++
> package/e3/e3.hash | 3 ++
> package/e3/e3.mk | 24 +++++++++
> 9 files changed, 210 insertions(+)
Do you really need/use this package? We already have several text
editors packaged, and this one is written in assembly, only usable on
i386/x86-64, requires patches from Gentoo, Fedora and Debian to build,
some of them being many years old, showing a project that is poorly
maintained.
This doesn't seem like a very useful addition to Buildroot to be
honest. Do you have some convincing arguments? :-)
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-27 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 13:03 [Buildroot] [PATCH 1/1] package/e3: new package Bernd Kuhls
2022-07-27 9:51 ` Thomas Petazzoni via buildroot [this message]
[not found] ` <20220727115113.0d06fb96__9944.83321426145$1658915496$gmane$org@windsurf>
2022-07-27 10:16 ` Bernd Kuhls
2022-07-27 10:24 ` Arnout Vandecappelle
2022-07-27 12:31 ` Bernd Kuhls
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=20220727115113.0d06fb96@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=thomas.petazzoni@bootlin.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