On Tue, Oct 5, 2021 at 10:37 PM Ulrich Mueller wrote:
>
> > On Tue, 05 Oct 2021, Alec Warner wrote:
>
> > I'd argue we can add NOTES.md to packages (e.g. allow those files.)
> > Then we modify packages.gentoo.org to render the markdown; or users
> > can render locally or read unrendered.
>
> H
> On Tue, 05 Oct 2021, Alec Warner wrote:
> I'd argue we can add NOTES.md to packages (e.g. allow those files.)
> Then we modify packages.gentoo.org to render the markdown; or users
> can render locally or read unrendered.
How would you deal with translations? One NOTES file for every languag
> On Tue, 05 Oct 2021, Sam James wrote:
> +Notes element
> +~
> +
> +The element describes important information on how to maintain
> +a package.
> +
> +The element has an obligatory ``type=""`` attribute whose value
> is
> +can be either ``text`` or ``url``. If its val
> On Tue, 05 Oct 2021, Michał Górny wrote:
> On Tue, 2021-10-05 at 19:27 +0100, Sam James wrote:
>> This is a preliminary version/draft of a proposed change to
>> GLEP 68.
>>
>> I'd like to introduce a method for developers to signal anything
>> special about a package and how to correctly ma
I can proxy-maint this if no real devs want it
El mar., 5 de octubre de 2021 10:23 p. m., Sam James
escribió:
> Hi,
>
> Putting app-text/mupdf up for grabs because I've not used it for a while.
>
> It needs a version bump (1.19.0) and some minor patches rebasing.
>
> Please note that anyone taki
Hi,
Putting app-text/mupdf up for grabs because I've not used it for a while.
It needs a version bump (1.19.0) and some minor patches rebasing.
Please note that anyone taking this over should keep an eye on upstream's
git occasionally to look for security relevant patches.
Best,
sam
signature
On 10/5/2021 16:29, Alec Warner wrote:
> I thought we were going to go with the github-pages type route
> (markdown, rendered online or locally.)
>
> -A
>
> On Tue, Oct 5, 2021 at 11:28 AM Sam James wrote:
>>
>> This is a preliminary version/draft of a proposed change to
>> GLEP 68.
>>
>> I'd li
>
> I generally agree that comments are more visible/noticeable than
> metadata, however, I also think that this could be a good step forward
> for overall maintainability. The issue with documenting these things
> in comments is that the comment lives only within the specific version
> of the ebu
> On 5 Oct 2021, at 18:43, Mike Gilbert wrote:
>
> Signed-off-by: Mike Gilbert
> ---
> .../2021-10-08-openssh-rsa-sha1.en.txt| 26 +++
> 1 file changed, 26 insertions(+)
> create mode 100644
> 2021-10-08-openssh-rsa-sha1/2021-10-08-openssh-rsa-sha1.en.txt
>
> diff --gi
On Tue, Oct 5, 2021 at 1:36 PM Sam James wrote:
>
>
>
> > On 5 Oct 2021, at 21:29, Alec Warner wrote:
> >
> > I thought we were going to go with the github-pages type route
> > (markdown, rendered online or locally.)
> >
>
> So, the thinking was, we could allow somewhat shorthand
> notes or for t
On Tue, Oct 5, 2021 at 4:22 PM Aaron W. Swenson wrote:
>
>
> I think it may be helpful to include the specific file(s) those
> options
> need to be added and to clarify whether they need to be added to
> the
> server host or the clients.
>
> Perhaps like so:
>
> hashes may be re-enabled on the
On Mon, Oct 4, 2021 at 2:48 AM Michał Górny wrote:
>
> On Tue, 2021-09-28 at 17:36 +0200, Michał Górny wrote:
> > I know I'm going to regret asking this... but I've prepared a change to
> > the Portage output format and I think it asks for a wider discussion
> > than internally in Portage team.
>
> On 5 Oct 2021, at 21:29, Alec Warner wrote:
>
> I thought we were going to go with the github-pages type route
> (markdown, rendered online or locally.)
>
So, the thinking was, we could allow somewhat shorthand
notes or for the people who want to invest more time, allow
the GitHub-pages typ
I thought we were going to go with the github-pages type route
(markdown, rendered online or locally.)
-A
On Tue, Oct 5, 2021 at 11:28 AM Sam James wrote:
>
> This is a preliminary version/draft of a proposed change to
> GLEP 68.
>
> I'd like to introduce a method for developers to signal anythi
I think it may be helpful to include the specific file(s) those
options
need to be added and to clarify whether they need to be added to
the
server host or the clients.
Perhaps like so:
hashes may be re-enabled on the server by adding the following
config
options to the end of /et
> Maybe we could just add README files to the package directories
> in question. This would have the clear advantage that the files will be
> immediately visible.
>
I'll personally prefer a readme.
Also almost all metadata.xml features are underused
>
On 10/2/21 10:51 AM, Mike Gilbert wrote:
> On Sat, Oct 2, 2021 at 1:25 PM A Schenck wrote:
>> Further discussion belongs on a different list, but the link provided by
>> mgorny and repeated by you does not allow collaborating in compliance
>> with the Gentoo Social Contract.
> The patches were als
On Tue, Oct 5, 2021 at 3:10 PM Mike Gilbert wrote:
>
> On Tue, Oct 5, 2021 at 2:27 PM Sam James wrote:
> >
> > This adds a new '' element to allow maintainers to describe
> > package-specific quirks or other instructions on how to correctly
> > maintain a package. This is intended to encourage de
On Tue, Oct 5, 2021 at 2:27 PM Sam James wrote:
>
> This adds a new '' element to allow maintainers to describe
> package-specific quirks or other instructions on how to correctly
> maintain a package. This is intended to encourage developers to document
> knowledge and increase the bus-factor of
On Tue, 2021-10-05 at 19:27 +0100, Sam James wrote:
> This is a preliminary version/draft of a proposed change to
> GLEP 68.
>
> I'd like to introduce a method for developers to signal anything
> special about a package and how to correctly maintain it.
>
> Sam James (1):
> glep-0068: Add notes
This adds a new '' element to allow maintainers to describe
package-specific quirks or other instructions on how to correctly
maintain a package. This is intended to encourage developers to document
knowledge and increase the bus-factor of packages which are delicate
but must live beyond a maintain
This is a preliminary version/draft of a proposed change to
GLEP 68.
I'd like to introduce a method for developers to signal anything
special about a package and how to correctly maintain it.
Sam James (1):
glep-0068: Add notes element for package maintenance instructions
glep-0068.rst | 26 +
Signed-off-by: Mike Gilbert
---
.../2021-10-08-openssh-rsa-sha1.en.txt| 26 +++
1 file changed, 26 insertions(+)
create mode 100644
2021-10-08-openssh-rsa-sha1/2021-10-08-openssh-rsa-sha1.en.txt
diff --git a/2021-10-08-openssh-rsa-sha1/2021-10-08-openssh-rsa-sha1.en.txt
On 2021-10-05 05:04, Sam James wrote:
Hi all,
Chainsaw asked retirement@ to drop him to maintainer-needed on his packages, so
here's the resultant
packages with no maintainers left:
app-admin/ansible-lint
> dev-python/requests-credssp
I'll take these.
--
Marecki
OpenPGP_signature
Des
Hi,
On 2021/10/05 05:04, Sam James wrote:
> Hi all,
>
> Chainsaw asked retirement@ to drop him to maintainer-needed on his packages,
> so here's the resultant
> packages with no maintainers left:
That's a shame. Big loss.
> app-arch/rpm
createrepo_c depends on this, willing to grab it purely f
On 05-10-2021 09:35:32 +0200, Michał Górny wrote:
> On Thu, 2021-09-30 at 09:18 +0200, Fabian Groffen wrote:
> > > > Final question, am I understanding correctly that normal lines are not
> > > > prefixed with something? Would it be, for consistency, alignment, and
> > > > certainty of selecting r
On Thu, 2021-09-30 at 09:18 +0200, Fabian Groffen wrote:
> > > Final question, am I understanding correctly that normal lines are not
> > > prefixed with something? Would it be, for consistency, alignment, and
> > > certainty of selecting rows something to use a prefix for those lines
> > > too (a
27 matches
Mail list logo
