From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Danilo Bargen <mail@dbrgn.ch>
Cc: Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/tealdeer: exclude unsupported targets
Date: Sun, 11 Dec 2022 18:17:35 +0100 [thread overview]
Message-ID: <20221211171735.GV1044805@scaer> (raw)
In-Reply-To: <b8157c6b-cf89-4d3d-bafc-fba182f8cf5a@app.fastmail.com>
Danilo, All,
On 2022-12-08 16:48 +0100, Danilo Bargen spake thusly:
> > Side note: overall, if you take a step back, it is absolutely
> > mind-blowing that a simple application showing tldr pages has a
> > dependency on architecture-specific things. There is really no sane
> > reason to have such dependencies, but apparently the Rust ecosystem is
> > not completely sane... :-/
>
> The reason is that Tealdeer uses https://github.com/rustls/rustls for
> TLS, which depends on the "ring" library
[--SNIP--]
> Previously tealdeer used OpenSSL, but quite a few of the users had
> trouble with broken OpenSSL installations. Plus, it made
> cross-compilation and static builds much harder. Using rustls makes
> this much easier on the common platforms, but of course, this has
> certain limitations with regards to more obscure target architectures.
cross-compilation with openssl is very easu. It just works.
That static build is harder I consider that a benefit rather than a
deficiency. ;-]
> If you would rather remove tealdeer from Buildroot (because the config
> is getting too complex), that would be OK for me. Otherwise, I'd
> update my patch based on your suggestions.
I think what Thomas meant, was that it is a pity that we need a TLS
implementation just to read the equivalent of man-pages, which by virtue
of being local oalways work, and that that TLS implementation has
limitations on architectures, which man-pages do not...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-11 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 10:02 [Buildroot] [PATCH 1/1] package/tealdeer: exclude unsupported targets Danilo Bargen
2022-12-08 13:16 ` Thomas Petazzoni via buildroot
2022-12-08 15:48 ` Danilo Bargen
2022-12-11 17:17 ` Yann E. MORIN [this message]
2022-12-11 18:52 ` Danilo Bargen
2022-12-11 16:37 ` Yann E. MORIN
2022-12-21 15:41 ` Peter Korsgaard
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=20221211171735.GV1044805@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=mail@dbrgn.ch \
/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