[Dnssec-trigger] Reducing dnssec-trigger-script in favor of riggerd

W.C.A. Wijngaards wouter at nlnetlabs.nl
Mon May 14 12:39:39 UTC 2018


Hi Martin,

Thank you for the patches!  I have applied them to the source.

Best regards, Wouter

On 14/05/18 14:16, Martin Sehnoutka wrote:
> Hi,
> 
> I tried to modify autotools in a way that without the newly introduced
> switch there will be no difference. In other words, it should be fully
> optional.
> 
> Please contact me if you have any further questions.
> 
> Best regards,
> Martin Sehnoutka
> 
> On 05/14/2018 09:50 AM, W.C.A. Wijngaards wrote:
>> Hi Martin,
>>
>> It was held for moderation because it was too large.  I did not see
>> that, because I am not the owner of the list, but I have access and
>> moderated (a long list of spam held for moderation, and I found your
>> email in it, and approved it).
>>
>> In general I like contributions that improve the software, if it doesn't
>> cause additional complication (eg. some people's wish to move to
>> automake that removes support for a bunch of features was denied for
>> such reasons).
>>
>> Best regards, Wouter
>>
>> On 11/05/18 09:06, Martin Sehnoutka wrote:
>>> Hi,
>>>
>>> I sent those patches some time ago, but the mailing list responded, that
>>> the message is waiting for moderation. Any news on that?
>>>
>>> Best regards,
>>> Martin
>>>
>>> On 04/10/2018 09:54 AM, W.C.A. Wijngaards wrote:
>>>> Hi Martin,
>>>>
>>>> On 10/04/18 09:40, Martin Sehnoutka wrote:
>>>>> Hello,
>>>>>
>>>>> I am working on a project of migrating the functionality currently
>>>>> provided by the script into the daemon. The build system was modified in
>>>>> a way, that you can select which implementation you want during build
>>>>> time. It, of course, defaults to the Python implementation. I have also
>>>>> added support for simple unit testing and automatic RPM package build on
>>>>> push event. Regarding the code base, the "update" command from the
>>>>> script is available in the daemon as "update_all", so that they can live
>>>>> side by side:
>>>>> https://github.com/InfrastructureServices/dnssec-trigger/blob/master-fedora/riggerd/svr.c#L806
>>>>>
>>>>> Now, I would like to ask you, is it acceptable for you to receive this
>>>>> project as a series of patches over the mailing-list? I know there was a
>>>>
>>>> Sure just send the patches.  Sounds like it could be a nice improvement!
>>>>
>>>>> question about migration to Git some time ago, is it being considered?
>>>>
>>>> The repo is replicated to github by script, I believe.
>>>>
>>>> Best regards, Wouter
>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dnssec-trigger mailing list
>>>> dnssec-trigger at NLnetLabs.nl
>>>> https://open.nlnetlabs.nl/mailman/listinfo/dnssec-trigger
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> dnssec-trigger mailing list
>>> dnssec-trigger at NLnetLabs.nl
>>> https://open.nlnetlabs.nl/mailman/listinfo/dnssec-trigger
>>>
>>
>>
>>
>>
>> _______________________________________________
>> dnssec-trigger mailing list
>> dnssec-trigger at NLnetLabs.nl
>> https://open.nlnetlabs.nl/mailman/listinfo/dnssec-trigger
>>
> 
> 
> 
> _______________________________________________
> dnssec-trigger mailing list
> dnssec-trigger at NLnetLabs.nl
> https://open.nlnetlabs.nl/mailman/listinfo/dnssec-trigger
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.nlnetlabs.nl/pipermail/dnssec-trigger/attachments/20180514/2a331b4e/attachment.bin>


More information about the dnssec-trigger mailing list