From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: bpftrace: the man pages does not clash any more
Date: Wed, 01 Mar 2023 22:09:33 +0100 [thread overview]
Message-ID: <20230301210933.AYJTf3LXQ4xHaAEt3GQo-e2Kdfh-urvCrDuZcbI6Pqs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42514@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2836 bytes --]
There's a closed pull request on the void-packages repository
bpftrace: the man pages does not clash any more
https://github.com/void-linux/void-packages/pull/42514
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
The man pages for bpftrace does not clash with bcc-tools man pages any more.
Tagging the maintainer @leahneukirchen
#### Testing the changes
- I tested the changes in this PR: **YES**
- Validation of the built package man pages against bcc-tools:
```
❯ xbps-query -f bpftrace | grep man8 | grep -v '\.bt\.'
/usr/share/man/man8/bpftrace.8
❯ xbps-query -f bcc-tools | grep man8 | grep 'bpftrace'
❯ xbps-query -f bpftrace | grep man8 | grep '\.bt\.'
/usr/share/man/man8/bashreadline.bt.8
/usr/share/man/man8/biolatency.bt.8
/usr/share/man/man8/biosnoop.bt.8
/usr/share/man/man8/biostacks.bt.8
/usr/share/man/man8/bitesize.bt.8
/usr/share/man/man8/capable.bt.8
/usr/share/man/man8/cpuwalk.bt.8
/usr/share/man/man8/dcsnoop.bt.8
/usr/share/man/man8/execsnoop.bt.8
/usr/share/man/man8/gethostlatency.bt.8
/usr/share/man/man8/killsnoop.bt.8
/usr/share/man/man8/loads.bt.8
/usr/share/man/man8/mdflush.bt.8
/usr/share/man/man8/naptime.bt.8
/usr/share/man/man8/oomkill.bt.8
/usr/share/man/man8/opensnoop.bt.8
/usr/share/man/man8/pidpersec.bt.8
/usr/share/man/man8/runqlat.bt.8
/usr/share/man/man8/runqlen.bt.8
/usr/share/man/man8/setuids.bt.8
/usr/share/man/man8/ssllatency.bt.8
/usr/share/man/man8/sslsnoop.bt.8
/usr/share/man/man8/statsnoop.bt.8
/usr/share/man/man8/swapin.bt.8
/usr/share/man/man8/syncsnoop.bt.8
/usr/share/man/man8/syscount.bt.8
/usr/share/man/man8/tcpaccept.bt.8
/usr/share/man/man8/tcpconnect.bt.8
/usr/share/man/man8/tcpdrop.bt.8
/usr/share/man/man8/tcplife.bt.8
/usr/share/man/man8/tcpretrans.bt.8
/usr/share/man/man8/tcpsynbl.bt.8
/usr/share/man/man8/threadsnoop.bt.8
/usr/share/man/man8/undump.bt.8
/usr/share/man/man8/vfscount.bt.8
/usr/share/man/man8/vfsstat.bt.8
/usr/share/man/man8/writeback.bt.8
/usr/share/man/man8/xfsdist.bt.8
❯ xbps-query -f bcc-tools | grep man8 | grep '\.bt\.'
❯
```
- bcc-tools can be cleanly installed alongside bpftrace
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
prev parent reply other threads:[~2023-03-01 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 21:50 [PR PATCH] " robertek
2023-03-01 21:09 ` leahneukirchen [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=20230301210933.AYJTf3LXQ4xHaAEt3GQo-e2Kdfh-urvCrDuZcbI6Pqs@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).