From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Core Update 171: Ship libsodium
Date: Tue, 27 Sep 2022 09:16:38 +0100 [thread overview]
Message-ID: <9B307A13-3D4F-4B73-8D94-F463B0BA7B2C@ipfire.org> (raw)
In-Reply-To: <9c35618c-d07b-a8c3-7e98-44e04787b152@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]
Hello Adolf,
Sorry, I overlooked that question.
I am currently fairly indifferent about this, but since the library is kind of small, it might be a better idea to have it as part of the core system.
-Michael
> On 27 Sep 2022, at 09:09, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> On 18/09/2022 12:44, Adolf Belka wrote:
>> Hi Michael,
>>
>> On 18/09/2022 11:08, Michael Tremer wrote:
>>> Why?
>> Because dnsdist has the default for the configure option of --with-libsodium set to auto so in the p[ast dnsdist was built without linking to libsodium. With the introduction of libsodium into the build dnsdist automatically found it and linked to it.
>>
>> So when libsodium was not shipped then dnsdist fails because it can't find the linked libsodium.so.23 file.
>>
>> If you don't want to ship libsodium, then the other alternative is that I can raise a patch to add --without-libsodium to the dnsdist configure. That will make it build and run with libsodium being in the build but not in the shipped core packages.
>>
>> Which way should I do this?
>>
> Is there a decision made about which option to use?
> - Ship libsodium in core IPFire
> - Build dnsdist without libsodium
>
> Regards,
> Adolf
>> Regards,
>>
>> Adolf.
>>>
>>>> On 17 Sep 2022, at 23:09, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
>>>>
>>>> On 17/09/2022 18:53, Peter Müller wrote:
>>>>> Fixes: #12929
>>>>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>>>>> ---
>>>>> config/rootfiles/core/171/filelists/libsodium | 1 +
>>>>> 1 file changed, 1 insertion(+)
>>>>> create mode 120000 config/rootfiles/core/171/filelists/libsodium
>>>>>
>>>>> diff --git a/config/rootfiles/core/171/filelists/libsodium b/config/rootfiles/core/171/filelists/libsodium
>>>>> new file mode 120000
>>>>> index 000000000..ebd862fbc
>>>>> --- /dev/null
>>>>> +++ b/config/rootfiles/core/171/filelists/libsodium
>>>>> @@ -0,0 +1 @@
>>>>> +../../../common/libsodium
>>>>> \ No newline at end of file
>>>>
>>>> --
>>>> Sent from my laptop
>>>
>
> --
> Sent from my laptop
next prev parent reply other threads:[~2022-09-27 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 16:53 Peter Müller
2022-09-17 21:09 ` Adolf Belka
2022-09-18 9:08 ` Michael Tremer
2022-09-18 10:44 ` Adolf Belka
2022-09-27 8:09 ` Adolf Belka
2022-09-27 8:16 ` Michael Tremer [this message]
2022-09-27 12:29 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9B307A13-3D4F-4B73-8D94-F463B0BA7B2C@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox