Proposal for removing some serialization limitations of define-configuration

2024-06-23 Thread Tomas Volf
Hello, I am trying to define configuration for my port of OpenBSD's acme-client, and got bit stuck with limitations of the define-configuration's serialization. First let me describe my problem (maybe there is a solution already). I want to generate this piece of configuration: authority le

New procedure to modify operating-system records

2024-06-23 Thread Sergio Pastor PĂ©rez
Hello Guix. Some time ago, I disclosed on this mailing list that I was working on a procedure to facilitate modifications of Guile records. The idea was to be able to easily apply transformations to all `operating-system` record packages. I received a lot of help from Michal Atlas and Juliana Sim

Re: Proposal for removing some serialization limitations of define-configuration

2024-06-23 Thread Development of GNU Guix and the GNU System distribution.
Hi Tomas, On Sun, Jun 23 2024, Tomas Volf wrote: > 1. I need the serializer for `name' field to wrap the output of other >serializers. Is it possible with nested configuration records (which I remember are complicated to set up)? > 2. I need to serialize key-file and key-type as one (since

Re: Proposal for removing some serialization limitations of define-configuration

2024-06-23 Thread Attila Lendvai
> authority letsencrypt { > api url "https://acme-v02.api.letsencrypt.org/directory"; > account key "/some/path.pem" rsa > contact "mailto:who@knows"; > } i have no time to verify this right now, but i think you should be able to write only the header and the wrapper in your custom serializer, a