From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-debug
Date: Sun, 07 Jan 2024 13:20:45 +0000 [thread overview]
Message-ID: <87wmslnuru.fsf@gentoo.org> (raw)
In-Reply-To: <25e92c7126ffcc566c1cb1fb671de16d706ff4fa.camel@gentoo.org>
Michał Górny <mgorny@gentoo.org> writes:
> [[PGP Signed Part:Undecided]]
> Hi,
>
> I'd like to propose adding a new dev-debug category. The description
> could be:
>
> Code debuggers and debugging-related tools.
Sounds good.
>
> Potential candidates include:
>
> [...]
dev-util/seer as well would be a good fit.
>
> This was originally prompted by bug 920438 [1], pointing out that LLDB
> and GDB belong to the same category. dev-util/ currently carries 428
> packages, so I suppose it makes sense to split it some more, especially
> when we can clearly distinguish some more specific groups.
>
Does anything dominate dev-util post-move or is it a real mix?
> [1] https://bugs.gentoo.org/920438
next prev parent reply other threads:[~2024-01-07 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 12:48 [gentoo-dev] [RFC] New category: dev-debug Michał Górny
2024-01-07 13:20 ` Sam James [this message]
2024-01-07 13:30 ` Michał Górny
2024-01-10 8:23 ` Florian Schmaus
2024-01-10 11:01 ` Sam James
2024-01-10 11:09 ` Florian Schmaus
2024-01-10 13:41 ` Viorel Munteanu
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=87wmslnuru.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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