public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] verifying profiles/package.mask comment format
@ 2021-02-21  4:30 Tim Harder
  2021-02-21  4:41 ` Sam James
  0 siblings, 1 reply; 2+ messages in thread
From: Tim Harder @ 2021-02-21  4:30 UTC (permalink / raw
  To: gentoo-dev

Hi all,

Is there interest in enforcing some basic QA for the semi-formatted
comments in profiles/package.mask (and possibly other profiles file
types)? I have code implementing the basic functionality done for
pkgcheck, but wondered if the format should be standardized and
documented more than it may be already before support is merged.

Also, I'm unsure it's been noticed but `pkgcheck scan --commits` now
verifies any profile changes done in git commits so this support would
automatically get run for package.mask changes (and other enabled files)
when using pkgcheck locally in that fashion.

Thanks,
Tim


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-dev] verifying profiles/package.mask comment format
  2021-02-21  4:30 [gentoo-dev] verifying profiles/package.mask comment format Tim Harder
@ 2021-02-21  4:41 ` Sam James
  0 siblings, 0 replies; 2+ messages in thread
From: Sam James @ 2021-02-21  4:41 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]


> On 21 Feb 2021, at 04:30, Tim Harder <radhermit@gentoo.org> wrote:
> 
> Hi all,
> 
> Is there interest in enforcing some basic QA for the semi-formatted
> comments in profiles/package.mask (and possibly other profiles file
> types)? I have code implementing the basic functionality done for
> pkgcheck, but wondered if the format should be standardized and
> documented more than it may be already before support is merged.
> 

I definitely have interest in this. Every so often, I find a class of mistakes
like incorrectly-ordered masks, wrong email format, and so on, and fix
them in the area I’m touching as it’s cheap to fix whatever file I’m on -
not necessarily so to fix every single one in profiles/.

This also gives us scope to make requirements like e.g. a bug reference,
clear date for removal if last-rites, and generally be a bit more verbose
by making clear what the expectations are for message content.

(There is a clear benefit for last-rites having at least one bug — it gives
users a chance to object or mention alternatives.)

Anyway, not trying to bikeshed re last-rites process, I just mean there’s
definitely a collection of uses here. Thanks for working on it.

Note that this was brought up last month too by jstein, so there is definitely other
interest: https://archives.gentoo.org/gentoo-dev/message/0600146362529770aa88225b29de46ae.

> Also, I'm unsure it's been noticed but `pkgcheck scan --commits` now
> verifies any profile changes done in git commits so this support would
> automatically get run for package.mask changes (and other enabled files)
> when using pkgcheck locally in that fashion.
> 
> Thanks,
> Tim
> 


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-02-21  4:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-02-21  4:30 [gentoo-dev] verifying profiles/package.mask comment format Tim Harder
2021-02-21  4:41 ` Sam James

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox