Date: Sat, 1 Jan 2022 17:10:37 +0100 From: Michael Gmelin <grembo@freebsd.org> To: Michael Fiano <mfml@fastmail.com> Cc: FreeBSD ports <freebsd-ports@freebsd.org> Subject: Re: Outdated ports Message-ID: <688DA8C3-5CD4-4933-AC25-FF426DDA7A0A@freebsd.org> In-Reply-To: <797318d3-d768-4837-a9ba-6579f8f9b6cb@www.fastmail.com> References: <797318d3-d768-4837-a9ba-6579f8f9b6cb@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-7CBF7089-18DE-4DBC-874D-EC5B573ED2AF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On 1. Jan 2022, at 16:00, Michael Fiano <mfml@fastmail.com> wrote: >=20 > =EF=BB=BFForgive me if this is not the correct forum. I've only been using= FreeBSD for a a couple months after a couple decades of Linux, and I notice= d some popular projects have ports that are severely out-dated: >=20 > sysutils/dunst is behind 5 releases, nearly a year old. > x11/rofi is behind 4 releases, more than a year old. >=20 > There were some others too, but these are the ones I remember. I was under= the impression that ports were kept fairly up to date. I am also aware that= this is volunteer work and someone might have to be nudged. Can someone po= int me to the correct approach here? Open a PR at https://bugs.FreeBSD.org, make sure to select the correct categ= ory (ports) and use the ports origin as the prefix of the subject line, this= will make sure it gets assigned to the maintainer automatically (e.g., "edi= tors/joe: Update to version 9.13"). If you feel ambitious, you can also attach a patch to do the update to help t= he maintainer. This would also allow a committer to help, in case there is n= o reaction from the maintainer within a couple of weeks. You can find more information on how to write PRs here: https://docs.freebsd= .org/en/articles/problem-reports/#pr-writing Best Michael --Apple-Mail-7CBF7089-18DE-4DBC-874D-EC5B573ED2AF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr"><br= ></div><div dir=3D"ltr"><br><blockquote type=3D"cite">On 1. Jan 2022, at 16:= 00, Michael Fiano <mfml@fastmail.com> wrote:<br><br></blockquote></div= ><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<span>Forgive me if thi= s is not the correct forum. I've only been using FreeBSD for a a couple mont= hs after a couple decades of Linux, and I noticed some popular projects have= ports that are severely out-dated:</span><br><span></span><br><span>sysutil= s/dunst is behind 5 releases, nearly a year old.</span><br><span>x11/rofi is= behind 4 releases, more than a year old.</span><br><span></span><br><span>T= here were some others too, but these are the ones I remember. I was under th= e impression that ports were kept fairly up to date. I am also aware that th= is is volunteer work and someone might have to be nudged. Can someone p= oint me to the correct approach here?</span><br></div></blockquote><br><div>= Open a PR at https://bugs.FreeBSD.org, make sure to select the correct categ= ory (ports) and use the ports origin as the prefix of the subject line, this= will make sure it gets assigned to the maintainer automatically (e.g., "edi= tors/joe: Update to version 9.13").</div><div><br></div><div>If you feel amb= itious, you can also attach a patch to do the update to help the maintainer.= This would also allow a committer to help, in case there is no reaction fro= m the maintainer within a couple of weeks.</div><div><br></div><div>You can f= ind more information on how to write PRs here: <a href=3D"https://docs.= freebsd.org/en/articles/problem-reports/#pr-writing">https://docs.freebsd.or= g/en/articles/problem-reports/#pr-writing</a></div><div><br></div><div>Best<= /div><div>Michael</div><div><br></div><div><br></div><div><br></div><div><br= ></div><div><br></div><div><br></div></body></html>= --Apple-Mail-7CBF7089-18DE-4DBC-874D-EC5B573ED2AF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?688DA8C3-5CD4-4933-AC25-FF426DDA7A0A>