Re: POD formatter version comments

--000000000000003dfa06141f32f3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 20, 2024 at 2:28=E2=80=AFAM Graham Knop <[email protected]> wrote=
:

> On Fri, Mar 15, 2024 at 7:55=E2=80=AFPM Shawn H Corey <shawnhcorey@gmail.=
com> wro
> I guess I wasn't clear. I was talking about making the requirement an
> option for the formatters. When the user runs a formatter, they can speci=
fy
> an option to include the info in their output. In other words, move it fr=
om
> a requirement to an optional implementation for a formatter.
>
> Formatters can implement whatever options they want, and can output
> however they want. What is the purpose of stating this specific option
> as something they can do? It can't be standardized, because it will
> inherently be dependent on the output format.
>

 I believe the paragraph in the docs should stay, but change the MUST to a
SHOULD, with a proviso that there should be a way to disable it (for the
purposes of repeatable builds etc). If the paragraph is removed entirely,
no one will implement it (the fact that it is not well-implemented now is
sad, but beside the point). I have no strong feelings as to whether the
option should default to on or off, but the option should exist for those
that wish this extra content.

--000000000000003dfa06141f32f3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Wed, Mar 20, 2024 at 2:28=E2=80=AFAM Graham Knop &lt;<a href=3D"m=
ailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">On Fri, Mar 15, 2024 at 7:55=E2=80=AF=
PM Shawn H Corey &lt;<a href=3D"mailto:[email protected]" target=3D"_bl=
ank">[email protected]</a>&gt; wro<br>
I guess I wasn&#39;t clear. I was talking about making the requirement an o=
ption for the formatters. When the user runs a formatter, they can specify =
an option to include the info in their output. In other words, move it from=
 a requirement to an optional implementation for a formatter.<br>
<br>
Formatters can implement whatever options they want, and can output<br>
however they want. What is the purpose of stating this specific option<br>
as something they can do? It can&#39;t be standardized, because it will<br>
inherently be dependent on the output format.<br></blockquote><div><br></di=
v><div>=C2=A0I believe the paragraph in the docs should stay, but change th=
e MUST to a SHOULD, with a proviso that there should be a way to disable it=
 (for the purposes of repeatable builds etc). If the paragraph is removed e=
ntirely, no one will implement it (the fact that it is not well-implemented=
 now is sad, but beside the point). I have no strong feelings as to whether=
 the option should default to on or off, but the option should exist for th=
ose that wish this extra content.</div><div><br></div><div><br></div></div>=
</div>

--000000000000003dfa06141f32f3--