From: Adolf Belka <adolf.belka@ipfire.org>
To: ummeegge <ummeegge@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Removal of JSON and commit 32c667786c1fb9bf5b0ddf1b091f092fd1ed23b8
Date: Thu, 27 Mar 2025 15:25:40 +0100 [thread overview]
Message-ID: <10193e11-b3c2-4189-9fbc-cac6f49fc881@ipfire.org> (raw)
In-Reply-To: <4e54134966d65b463a0968936b98419a5b833dd2.camel@ipfire.org>
Hi Erik,
On 26/03/2025 07:17, ummeegge wrote:
> Good morning Adolf,
> thanks for fixing/extending it. Have searched also for a `use JSON;`
> declaration in IPFire since i was not sure if the JSON modul has been
> used somewhere as a dependency. In this case the declaration would have
> caused errors but i have not found anything in IPFire´s code base.
It was being used by samba so the use command would be in their code.
Regards,
Adolf.
>
> Best,
>
> Erik
>
> Am Freitag, dem 21.03.2025 um 10:11 +0100 schrieb Adolf Belka:
>> Hi Erik,
>>
>> On 17/03/2025 07:33, ummeegge wrote:
>>> Hello Adolf,
>>> great thanks. Have seen it also only since i do needed them for a
>>> project.
>>
>> It is in CU193 Testing.
>>
>> Regards,
>> Adolf.
>>
>>>
>>> Best,
>>>
>>> Erik
>>>
>>> Am Samstag, dem 15.03.2025 um 17:41 +0100 schrieb Adolf Belka:
>>>> Hi Erik,
>>>>
>>>> On 13/03/2025 08:25, ummeegge wrote:
>>>>> Hi Adolf,
>>>>> have seen that you removed the perl-JSON Addon since it is now
>>>>> available in Perl´s core modules
>>>>> https://patchwork.ipfire.org/project/ipfire/patch/20240914152831.7727-8-adolf.belka@ipfire.org/
>>>>> . Perl´s ROOTFILE have the pp.pm
>>>>> commented
>>>>> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/rootfiles/
>>>>> common/perl;h=d4ceb7083ea32ce19c0befef168575696c244dd2;hb=refs/
>>>>> head
>>>>> s/next#l315
>>>>> so JSON has now been fully removed from IPFire.
>>>>>
>>>>> My question is, was this intended ?
>>>>
>>>> No that was not intended. I obviously missed that.
>>>>
>>>> I will submit a patch to uncomment the lines in the perl
>>>> rootfile.
>>>>
>>>> Regards,
>>>> Adolf.
>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>> Erik
>>>>
>>>
>>
>>
>
>
prev parent reply other threads:[~2025-03-27 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5f9a0c4912a941d9836af07f68e10e22b30a437e.camel@ipfire.org>
2025-03-15 16:41 ` Adolf Belka
[not found] ` <ba638428ff84a8873c27c829c7f523e028ad08d2.camel@ipfire.org>
2025-03-21 9:11 ` Adolf Belka
2025-03-26 6:17 ` ummeegge
2025-03-27 14:25 ` Adolf Belka [this message]
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=10193e11-b3c2-4189-9fbc-cac6f49fc881@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=ummeegge@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