public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New category: dev-debug
Date: Wed, 10 Jan 2024 12:09:17 +0100	[thread overview]
Message-ID: <07128d44-6223-419e-8331-6390cae50a0a@gentoo.org> (raw)
In-Reply-To: <875y01o3im.fsf@gentoo.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1024 bytes --]

On 10/01/2024 12.01, Sam James wrote:
> 
> Florian Schmaus <flow@gentoo.org> writes:
> 
>> [[PGP Signed Part:Undecided]]
>> On 07/01/2024 13.48, Michał Górny wrote:
>>> Hi,
>>> I'd like to propose adding a new dev-debug category.  The
>>> description
>>> could be:
>>>     Code debuggers and debugging-related tools.
>>
>> Seems sensible. I'd probably drop the "Code" from the description,
>> since packages like d-spy do not primarily debug code.
>>
>> I assume profilers are explicitly not part of this category?
> 
> leio had the same question and we came up with a list of about 5-6
> packages at least which would fit in a dev-profile category...

Right and a sensible next step would probably be an extra category for 
those.

The problem is that that the lines between profilers, tracers, and 
performance counter tools sometimes gets blurry. But I think it could be 
fine to shove those all into one category, but maybe dev-perf then 
(e.g., "Tools for performance analysis")?

- Flow

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17273 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2024-01-10 11:09 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
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 [this message]
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=07128d44-6223-419e-8331-6390cae50a0a@gentoo.org \
    --to=flow@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