From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.3.4 released
Date: Tue, 24 Mar 2020 20:11:10 -0600 [thread overview]
Message-ID: <CAHmME9os=HxxxqWHp9nM6ggDdkqwpa6gOpTTAG68gamR3NtWaA@mail.gmail.com> (raw)
In-Reply-To: <20200323222041.uzfcexg2wy74jqdd@chatter.i7.local>
Hi Konstantin,
Still not a fan at all of the attestation stuff, but the lore
integration is a great convenience. Thanks for this great tool. I've
packaged it up for Gentoo:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8374a4402f40ad1ff3613e281db5bb897708fcea
Users can now run:
`$ emerge b4`
Please let me know if any of the metadata I've used in that commit is
off. As well, at the bottom of this email is a listing of all the
files this winds up installing, in case you spot something as being
wrong.
Will you continue to send release announcements here, or should I set
up a notifier through other means?
I'm curious to learn: where did this name "b4" come from? Is it like
the millennial meme phrase "inb4" being a deconstruction of "inbox"
for a postmodern command line work of art?
Regards,
Jason
----8<--------------------------
zx2c4@thinkpad ~ $ equery f b4
* Searching for b4 ...
* Contents of net-mail/b4-0.3.4:
/usr
/usr/bin
/usr/bin/b4 -> ../lib/python-exec/python-exec2
/usr/lib
/usr/lib/python-exec
/usr/lib/python-exec/python3.6
/usr/lib/python-exec/python3.6/b4
/usr/lib64
/usr/lib64/python3.6
/usr/lib64/python3.6/site-packages
/usr/lib64/python3.6/site-packages/b4
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info/PKG-INFO
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info/SOURCES.txt
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info/dependency_links.txt
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info/entry_points.txt
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info/requires.txt
/usr/lib64/python3.6/site-packages/b4-0.3.4-py3.6.egg-info/top_level.txt
/usr/lib64/python3.6/site-packages/b4/__init__.py
/usr/lib64/python3.6/site-packages/b4/__pycache__
/usr/lib64/python3.6/site-packages/b4/__pycache__/__init__.cpython-36.opt-1.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/__init__.cpython-36.opt-2.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/__init__.cpython-36.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/attest.cpython-36.opt-1.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/attest.cpython-36.opt-2.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/attest.cpython-36.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/command.cpython-36.opt-1.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/command.cpython-36.opt-2.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/command.cpython-36.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/mbox.cpython-36.opt-1.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/mbox.cpython-36.opt-2.pyc
/usr/lib64/python3.6/site-packages/b4/__pycache__/mbox.cpython-36.pyc
/usr/lib64/python3.6/site-packages/b4/attest.py
/usr/lib64/python3.6/site-packages/b4/command.py
/usr/lib64/python3.6/site-packages/b4/mbox.py
/usr/share
/usr/share/doc
/usr/share/doc/b4-0.3.4
/usr/share/doc/b4-0.3.4/README.rst.bz2
next prev parent reply other threads:[~2020-03-25 2:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 22:20 b4 v0.3.4 released Konstantin Ryabitsev
2020-03-25 2:11 ` Jason A. Donenfeld [this message]
2020-03-25 2:19 ` [kernel.org users] " Jason A. Donenfeld
2020-03-25 15:05 ` Konstantin Ryabitsev
2020-03-25 15:26 ` Konstantin Ryabitsev
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11 ` Rob Herring
2020-03-26 16:16 ` Konstantin Ryabitsev
2020-03-26 16:27 ` James Bottomley
2020-03-26 16:31 ` Geert Uytterhoeven
[not found] ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32 ` Konstantin Ryabitsev
2020-03-26 20:18 ` Jason A. Donenfeld
2020-03-27 18:15 ` Konstantin Ryabitsev
2020-04-06 21:53 ` Konstantin Ryabitsev
2020-09-22 22:17 ` Rob Herring
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='CAHmME9os=HxxxqWHp9nM6ggDdkqwpa6gOpTTAG68gamR3NtWaA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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;
as well as URLs for NNTP newsgroup(s).