From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Danilo Bargen" <mail@dbrgn.ch>
Cc: Romain Naour <romain.naour@smile.fr>,
Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/tealdeer: new package
Date: Wed, 27 Jul 2022 22:56:47 +0200 [thread overview]
Message-ID: <20220727225647.480ad013@windsurf> (raw)
In-Reply-To: <1494d3a9-0b16-45fe-99f4-9b8d0bd28aad@www.fastmail.com>
Hello Danilo,
On Wed, 27 Jul 2022 22:25:06 +0200
"Danilo Bargen" <mail@dbrgn.ch> wrote:
> For a purely embedded headless system, the package is not really
> useful, but on a system where administrators actively log in (e.g. a
> system accessible via SSH, with some administration tools
> preinstalled) it may be useful as a local command-line based
> reference documentation for commonly used tools and commands.
>
> I looked at the list of existing packages, and it includes packages
> like htop which are primarily used for system administration, so I
> figured tealdeer might be welcome as well.
htop is a tool for system monitoring/performance analysis. You can't
run "htop" on your PC to get the information about your target, while
you can run tldr on your PC to get any tldr page, just like on your
target. So you can't compare htop and tldr.
> On the other hand, if you decide that man pages are excluded from a
> target system, then I'd understand if you'd reject the package.
man pages are removed from the target filesystem in Buildroot,
unconditionally. From the target-finalize target in the main Makefile:
rm -rf $(TARGET_DIR)/usr/man $(TARGET_DIR)/usr/share/man
rm -rf $(TARGET_DIR)/usr/info $(TARGET_DIR)/usr/share/info
rm -rf $(TARGET_DIR)/usr/doc $(TARGET_DIR)/usr/share/doc
> One could argue though that tealdeer does not ship any tldr pages
> when installing. All tldr pages are fetched and cached at runtime,
> unlike man pages, where including them for all packages would bloat
> the target image.
It is true that is less heavy than man pages in that regard.
In any case, the patch is applied. I just thought it was useful to
share the discussion/concern we had when discussing whether to merge or
not this new package.
Best regards,
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
prev parent reply other threads:[~2022-07-27 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 23:18 [Buildroot] [PATCH 1/1] package/tealdeer: new package Danilo Bargen
2022-07-27 9:09 ` Romain Naour
2022-07-27 9:49 ` Thomas Petazzoni via buildroot
2022-07-27 20:25 ` Danilo Bargen
2022-07-27 20:56 ` Thomas Petazzoni via buildroot [this message]
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=20220727225647.480ad013@windsurf \
--to=buildroot@buildroot.org \
--cc=mail@dbrgn.ch \
--cc=romain.naour@smile.fr \
--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