Re: HEADS-UP: security/openssl switching to 3.0 branch

Tatsuki Makino wrote on 2023/10/18 09:06:
> pkg set -n openssl:openssl111
> pkg set -o security/openssl:security/openssl111
> Will these changes also update the local.sqlite deps table? :)

I have run it in my environment. in use :)
From the results of `pkg shell .dump | grep openssl`, it seems that the rewrite was done as I thought.
A few lines of examples are quoted below.

INSERT INTO packages VALUES(27078,'security/openssl111','openssl111','1.1.1w,1','TLSv1.3 capable SSL and crypto library',replace('T ...(omitted)
INSERT INTO deps VALUES('security/openssl111','openssl111','1.1.1w,1',22497);
INSERT INTO deps VALUES('security/openssl111','openssl111','1.1.1w,1',22958);

This changed the pkg version results as follows.

> pkg version -v -e openssl111
openssl111-1.1.1w,1                >   succeeds index (index has 1.1.1w)

Since PORTEPOCH is different, it seems that it needs to be rebuilt and reinstalled after all :)

By the way, security/openssl111 of origin has been disused once, around 2020-01-01.
And if it is used again, how will PORTEPOCH be treated?

Regards.