From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wtfutil: new package
Date: Thu, 21 Apr 2022 17:39:08 +0200 [thread overview]
Message-ID: <20220421153908.GN2730@scaer> (raw)
In-Reply-To: <8b28d775-d65a-d6e2-2b50-6bfc6549df0b@mind.be>
On 2022-04-21 09:22 +0200, Arnout Vandecappelle spake thusly:
> On 20/04/2022 22:01, Yann E. MORIN wrote:
> >Some of wtfutils modules (i.e. plugins) can call to external tools, so
> Modules are not optional?
As far as I can see, no. All modules are builtin into the wtfutil
executable, and there is no way to provide out-of-tree modules loaded at
runtime. And indeed, using the word 'plugins' was wrong (well, they can
only be plugged in at build time).
Also this is go, everything is static in that world.
Upstream would however like to go for an actual, real plugin mechanism,
but it seems the go ecosystem is not making that easy:
https://github.com/wtfutil/wtf/issues/1092#issuecomment-892312321
[--SNIP--]
> >+WTFUTIL_VERSION = 0.41.0
> >+WTFUTIL_SITE = $(call github,wtfutil,wtf,v$(WTFUTIL_VERSION))
> If the upstream repository is called wtf, and the help text says "WTF is
> ...", why do you call it wtfutil?
The website is wtfutil.com. The utility is named wtfutil. It is packaged
as wtfutil in some distro repositories already (Homebrew, macports,
Arch...).
The README.md also states:
WTF (aka 'wtfutil') is the personal information dashboard for your
terminal, providing at-a-glance access to your very important but
infrequently-needed stats and data.
Finally, wtf on its own is a bit on the tendentious side; using the
longer name tones the term down a bit.
Yeah, that is not all entirely convincing, but I believe wtfutil to be a
better name overall...
Regards,
Yann E. MORIN.
> Regards,
> Arnout
>
> >+WTFUTIL_LICENSE = MPL-2.0
> >+WTFUTIL_LICENSE_FILES = LICENSE.md
> >+
> >+$(eval $(golang-package))
--
.-----------------.--------------------.------------------.--------------------.
| 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-04-21 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 20:01 [Buildroot] [PATCH] package/wtfutil: new package Yann E. MORIN
2022-04-21 7:22 ` Arnout Vandecappelle
2022-04-21 15:39 ` Yann E. MORIN [this message]
2022-04-23 16:26 ` Arnout Vandecappelle
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=20220421153908.GN2730@scaer \
--to=yann.morin.1998@free.fr \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
/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