Ah ok, now makes sense.

> On Oct 25, 2022, at 1:22 PM, Stuart Henderson <s...@spacehopper.org> wrote:
> 
> If there are two versions of a library are in the ports tree, it must
> be possible to install them both at the same time, they may not conflict.
> 
> Otherwise there is a problem in bulk builds where one port depends
> on one version of the library, and another port depends on the other
> version.
> 
>> On 2022/10/25 12:56, Chris wrote:
>> Hello,
>> 
>> https://cvsweb.openbsd.org/ports/security/polarssl/Makefile
>> Not sure what you mean there is no mbedtls port, it's called polarssl and it
>> fetches mbedtls.
>> 
>> polarssl3 just install mbedtls 3.2.1 ?
>> 
>> Ideally this should be renamed to mbedtls/mbedtls-lts and mbedtls3
>> 
>> Chris
>> 
>>> On 10/25/2022 12:46 PM, Stuart Henderson wrote:
>>> On 2022/10/25 12:16, Chris wrote:
>>>> Hello,
>>>> 
>>>> Guess I should of asked first as ports has
>>>> https://openports.se/security/polarssl
>>> 
>>> btw openports.se is not an authoritative source and has various
>>> problems with its parsing of the ports tree.
>>> 
>>>> Reading the Makefile it mentions mbedtls but the name was
>>>> changed some time ago to mbedtls.
>>>> 
>>>> the LTS is the 2.28.1 and the current versions is 3.2.1
>>>> 
>>>> So I decided to create a polarssl3 keeping the current name.
>>> 
>>> To import this in a new directory it would need to be de-conflicted with
>>> the existing mbedtls port, but better to update the existing port
>>> ideally.
>>> 
>>>> Please find attached tar file as requested.
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>> 
>>>> On 10/25/2022 11:29 AM, Stuart Henderson wrote:
>>>>> On 2022/10/25 09:56, Chris wrote:
>>>>>> Hello,
>>>>>> 
>>>>>> First attempt at creating a new port for polarssl3 3.x version
>>>>> 
>>>>> Please don't send shars. CVS diff or git diff preferred for updates, tar
>>>>> for new ports.
>>>>> 
>>>>> To import this in a new directory it would need to be de-conflicted with
>>>>> the existing mbedtls port, but better to update the existing port
>>>>> ideally.
>>>>> 
>>> 
>>> 
> 

Reply via email to