Date: Mon, 17 Jul 2023 23:13:19 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Mark Millard <marklmi@yahoo.com> Cc: stb@lassitu.de, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: Can someone please post a concise list of things maintainers are supposed to do? Message-ID: <CAN6yY1vFDR_MwpVQN0vTBFo3sNvwGd6zOFGw-ofnYrTja5%2B3aw@mail.gmail.com> In-Reply-To: <67AAFD7F-CE3C-4051-ADE9-0646BCC16143@yahoo.com> References: <67AAFD7F-CE3C-4051-ADE9-0646BCC16143.ref@yahoo.com> <67AAFD7F-CE3C-4051-ADE9-0646BCC16143@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000beb8980600bcd07a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2023 at 7:31=E2=80=AFAM Mark Millard <marklmi@yahoo.com> wr= ote: > From: Stefan Bethke <stb_at_lassitu.de> wrote on > Date: Mon, 17 Jul 2023 07:04:11 UTC : > > > every time I submit a PR to update a port I maintain, I get conflicting > instructions about how to fill in the PR. This is really annoying, and so= me > committers apparently feel they will not move forward in processing the P= R > unless some bureaucratic bullshit is done. > > > > Can the ports team please provide a concise, definitive list on how a > maintainer is supposed to fill in a port update PR, so this nonsense stop= s? > > It might be useful to report the specific conflicting instructions > that you have received and to ask that the "definitive list" at least > resolve the specific conflicts. Otherwise the list might miss some > issues that you ran into. Right now there is no way for someone > generating a list to know up front if they have covered all your > example issues. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.co <http://yahoo.com>m This is an old issue. Many years ago I submitted a new port for the weird modem in an IBM ThinkPad. The committer who picked up the ticket insisted that some scripting involved be rewritten in Perl. I did so and finally got the port committed. Less than two weeks later it was announced that perl would be removed from the base system and that port scripts needed to be converted to sh. While I applaud the removal of perl, I asked what the "rules" were for structuring a port. Never got an answer. At least we now have portlint that eliminates a lot of these issues. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000beb8980600bcd07a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-family:tahoma,sans-serif;font-size:small">On Mon, Jul 17, 2023 at 7:31=E2= =80=AFAM Mark Millard <<a href=3D"mailto:marklmi@yahoo.com">marklmi@yaho= o.com</a>> wrote:</div></div><div class=3D"gmail_quote"><blockquote clas= s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r= gb(204,204,204);padding-left:1ex">From: Stefan Bethke <<a href=3D"http:/= /stb_at_lassitu.de" rel=3D"noreferrer" target=3D"_blank">stb_at_lassitu.de<= /a>> wrote on<br> Date: Mon, 17 Jul 2023 07:04:11 UTC :<br> <br> > every time I submit a PR to update a port I maintain, I get conflictin= g instructions about how to fill in the PR. This is really annoying, and so= me committers apparently feel they will not move forward in processing the = PR unless some bureaucratic bullshit is done.<br> > <br> > Can the ports team please provide a concise, definitive list on how a = maintainer is supposed to fill in a port update PR, so this nonsense stops?= <br> <br> It might be useful to report the specific conflicting instructions<br> that you have received and to ask that the "definitive list" at l= east<br> resolve the specific conflicts. Otherwise the list might miss some<br> issues that you ran into. Right now there is no way for someone<br> generating a list to know up front if they have covered all your<br> example issues.<br> <br> =3D=3D=3D<br> Mark Millard<br> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer" target=3D"_blank= ">yahoo.co</a><span class=3D"gmail_default" style=3D"font-family:tahoma,san= s-serif;font-size:small">m</span></blockquote><div>=C2=A0</div><div><div st= yle=3D"font-family:tahoma,sans-serif;font-size:small" class=3D"gmail_defaul= t">This is an old issue. Many years ago I submitted a new port for the weir= d modem in an IBM ThinkPad. The committer who picked up the ticket insisted= that some scripting involved be rewritten in Perl. I did so and finally go= t the port committed. Less than two weeks later it was announced that perl = would be removed from the base system and that port scripts needed to be co= nverted to sh. While I applaud the removal of perl, I asked what the "= rules" were for structuring a port. Never got an answer. At least we n= ow have portlint that eliminates a lot of these issues.<br></div></div></di= v><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" cla= ss=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir= =3D"ltr"><div><div dir=3D"ltr">Kevin Oberman, Part time kid herder and reti= red Network Engineer<br>E-mail: <a href=3D"mailto:rkoberman@gmail.com" targ= et=3D"_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB9= 8AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div= ></div></div> --000000000000beb8980600bcd07a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vFDR_MwpVQN0vTBFo3sNvwGd6zOFGw-ofnYrTja5%2B3aw>