Date: Sun, 28 Aug 2022 23:05:24 +0200 From: Michael Gmelin <grembo@freebsd.org> To: Pete Wright <pete@nomadlogic.org> Cc: FreeBSD <freebsd-ports@freebsd.org> Subject: Re: nginx-full version numbering question Message-ID: <6FB093FB-C867-4714-854A-7A03B021B83B@freebsd.org> In-Reply-To: <466807a8-2c28-d11d-a3bd-96beeb377af5@nomadlogic.org> References: <466807a8-2c28-d11d-a3bd-96beeb377af5@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-36512E02-B28E-49B0-BBEB-278A889969D6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On 28. Aug 2022, at 19:23, Pete Wright <pete@nomadlogic.org> wrote: >=20 > =EF=BB=BF hey there - i had a question about an apparent version numbering= issue with the nginx-full port: > https://www.freshports.org/www/nginx-full/ >=20 > on April 10th the version number is: 1.20.2_9,2 > then on the next update (may 31) the version number seems to go backwards:= 1.22.0_10,2 >=20 Hi Pete, What makes you think that 1.22.0 is smaller than 1.20.2? Cheers > i was curious if that was intended? this makes it a little awkward to upg= rade a locally patched version of the port from before May 31, as i'll have t= o uninstall then install to pick up the latest upstream (which contains a fi= x i was patching out of tree). >=20 > thanks! > -pete > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA --Apple-Mail-36512E02-B28E-49B0-BBEB-278A889969D6 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 28. Aug 2022, at 19= :23, Pete Wright <pete@nomadlogic.org> wrote:<br><br></blockquote></di= v><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF =20 <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8"= > =20 =20 <font face=3D"monospace">hey there - i had a question about an apparent version numbering issue with the nginx-full port:<br> <a class=3D"moz-txt-link-freetext" href=3D"https://www.freshports.org/= www/nginx-full/">https://www.freshports.org/www/nginx-full/</a><br>; <br> on April 10th the version number is:</font><font face=3D"monospace"><s= pan class=3D"element-details"> 1.20.2_9,2<br> then on the next update (may 31) the version number seems to go backwards: </span></font><font face=3D"monospace"><span class=3D"ele= ment-details"><span class=3D"element-details">1.22.0_10,2<br> <br></span></span></font></div></blockquote><div><br></div><div>Hi= Pete,</div><div><br></div><div>What makes you think that 1.22.0 is smaller t= han 1.20.2?</div><div><br></div><div>Cheers</div><div><br></div><div><br></d= iv><br><blockquote type=3D"cite"><div dir=3D"ltr"><font face=3D"monospace"><= span class=3D"element-details"><span class=3D"element-details"> i was curious if that was intended? this makes it a little awkward to upgrade a locally patched version of the port from before May 31, as i'll have to uninstall then install to pick up the latest upstream (which contains a fix i was patching out of tree).<br> <br> thanks!<br> -pete<br> </span></span></font> <pre class=3D"moz-signature" cols=3D"72">--=20 Pete Wright <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:pete@nomadlogic.org">pe= te@nomadlogic.org</a> @nomadlogicLA</pre> =20 </div></blockquote></body></html>= --Apple-Mail-36512E02-B28E-49B0-BBEB-278A889969D6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6FB093FB-C867-4714-854A-7A03B021B83B>