On 4.3.2022 2.35, Ionen Wolkens wrote:
> On Tue, Oct 05, 2021 at 02:21:22PM -0700, 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.
>>
>> WDYT?
On Tue, Oct 05, 2021 at 02:21:22PM -0700, 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.
>
> WDYT?
Given this topic came up again on IRC, late
> On Thu, 07 Oct 2021, Matthew Marchese wrote:
> I also like the idea of markdown files or RST files living in
> gentoo::. I personally find RST to be a bit more challenging to write,
> but it's simple enough to learn and we 'already have RST to HTML
> conversion on www.g.o for GLEPs. GitHub
On 10/5/21 12:09, 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 maintain it.
Sam James
> On Wed, 06 Oct 2021, Alec Warner wrote:
> On Tue, Oct 5, 2021 at 10:37 PM Ulrich Mueller wrote:
>> How would you deal with translations? One NOTES file for every language?
> The notes files are for devs, not for users. Do we have non-english
> speaking developers?
Sure, this is a
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.
>
>
> 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
> 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
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
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
> 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
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
> 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 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
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
15 matches
Mail list logo
