On 10/01/2024 16.10, Ulrich Mueller wrote:
On Wed, 10 Jan 2024, Florian Schmaus wrote:
On 10/01/2024 14.58, Ulrich Mueller wrote:
Looks like readme.gentoo-r1 already gives you control over this:
# If you want to show them always, please set FORCE_PRINT_ELOG to a non empty
# value in your
> On Wed, 10 Jan 2024, Florian Schmaus wrote:
> On 10/01/2024 14.58, Ulrich Mueller wrote:
>> Looks like readme.gentoo-r1 already gives you control over this:
>> # If you want to show them always, please set FORCE_PRINT_ELOG to a non empty
>> # value in your ebuild before this function is
On 10/01/2024 14.58, Ulrich Mueller wrote:
On Wed, 10 Jan 2024, Florian Schmaus wrote:
On 10/01/2024 12.04, Sam James wrote:
1) The name seems odd (why not readme.gentoo-r2)?
2) Why can't the existing eclass be improved?
Both points, the name of the eclass and the question if this should
Hi Sam,
On 2024/01/10 13:02, Sam James wrote:
Jaco Kroon writes:
How critical is it that they do?
Even for the bump PR they do not, they fail with the below, and
frankly my knowledge of ruby is outright scary. The below to me
indicates that the tests are designed specifically to run from a
> On Wed, 10 Jan 2024, Florian Schmaus wrote:
> On 10/01/2024 12.04, Sam James wrote:
>> 1) The name seems odd (why not readme.gentoo-r2)?
>> 2) Why can't the existing eclass be improved?
> Both points, the name of the eclass and the question if this should be
> added to the existing eclass
La 07.01.2024 14:48, Michał Górny a scris:
Hi,
I'd like to propose adding a new dev-debug category. The description
could be:
Code debuggers and debugging-related tools.
Potential candidates include:
dev-util/rr would be a good candidate too.
Regards,
Viorel
On 1/10/2024 6:51 AM, Sam James wrote:
>
> gentoo_bugs_p...@parallaxshift.com writes:
>
>> help
>
> ???
Whoops! Sorry about that. I brain farted and thought this was a
mailinglist control e-mail address. And I'm on the digest, so I hadn't
received my own stupidity sent back to myself yet.
On 10/01/2024 12.04, Sam James wrote:
Florian Schmaus writes:
I really like the functionality of readme.gentoo-r1.eclass, as it
allows to communicate Gentoo-specific information about a package to
the user. Especially as it improves the signal-to-noise ratio of
messages arriving to our
On 10/01/2024 12.01, Sam James wrote:
Florian Schmaus 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
Florian Schmaus writes:
> I really like the functionality of readme.gentoo-r1.eclass, as it
> allows to communicate Gentoo-specific information about a package to
> the user. Especially as it improves the signal-to-noise ratio of
> messages arriving to our users.
>
> However,
Jaco Kroon writes:
> Hi,
>
> On 2024/01/09 13:42, Michał Górny wrote:
>> On Tue, 2024-01-09 at 12:54 +0200, Jaco Kroon wrote:
>>> https://github.com/gentoo/gentoo/pull/34126 ??
>>>
>>> Perhaps I'm missing something if you say it's non-trivial but we're
>>> using that on 9 hosts currently.
>>>
Florian Schmaus 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"
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
13 matches
Mail list logo
