> On 29. Aug 2022, at 00:33, Pete Wright wrote:
>
> On Sun, Aug 28, 2022 at 11:05:24PM +0200, Michael Gmelin wrote:
>>
>>
On 28. Aug 2022, at 19:23, Pete Wright wrote:
>>>
>>> hey there - i had a question about an apparent version numbering issue
>>> with the nginx-full port:
>>>
On Sun, Aug 28, 2022 at 11:05:24PM +0200, Michael Gmelin wrote:
>
>
> > On 28. Aug 2022, at 19:23, Pete Wright wrote:
> >
> > 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
> On 28. Aug 2022, at 23:05, Michael Gmelin wrote:
>
>
>
>
>>> On 28. Aug 2022, at 19:23, Pete Wright wrote:
>>>
>> 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
> On 28. Aug 2022, at 19:23, Pete Wright wrote:
>
> 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 vers
Hello.
I'm not sure :), but we can use pkg version -t to find out how big or small the
port version is.
pkg version -t 1.20.2_9,2 1.22.0_10,2
is <.
www/nginx-full is the sl@ve port of the m@ster port www/nginx.
So, changes in the distfile version will automatically follow.
But then the sl@ve po
