Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Aug 2022 10:22:57 -0700
From:      Pete Wright <pete@nomadlogic.org>
To:        FreeBSD <freebsd-ports@freebsd.org>
Subject:   nginx-full version numbering question
Message-ID:  <466807a8-2c28-d11d-a3bd-96beeb377af5@nomadlogic.org>

next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------0DlffCtuQufaMU5GxXFJOIG6
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

hey there - i had a question about an apparent version numbering issue 
with the nginx-full port:
https://www.freshports.org/www/nginx-full/

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

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).

thanks!
-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA

--------------0DlffCtuQufaMU5GxXFJOIG6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="monospace">hey there - i had a question about an
      apparent version numbering issue with the nginx-full port:<br>
      <a class="moz-txt-link-freetext" href="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="monospace"><span
        class="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="monospace"><span
        class="element-details"><span class="element-details">1.22.0_10,2<br>
          <br>
          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="moz-signature" cols="72">-- 
Pete Wright
<a class="moz-txt-link-abbreviated" href="mailto:pete@nomadlogic.org">pete@nomadlogic.org</a>
@nomadlogicLA</pre>
  </body>
</html>

--------------0DlffCtuQufaMU5GxXFJOIG6--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?466807a8-2c28-d11d-a3bd-96beeb377af5>