support toml configuration #209

Open
opened 2024-04-02 15:24:27 +00:00 by jade · 3 comments
Owner

our config format is bad. upstream wants to use json. we do not. we have a toml parser, let's just do that.

likely implementation plan:

  • support both configs
  • stop adding features to the old one
  • leave it to bake for a while
  • delete the old one in a year or two after putting a warning in the NixOS module that extraConfig is b&, and a proper deprecation cycle and migration
our config format is bad. upstream wants to use json. we do not. we have a toml parser, let's just do that. likely implementation plan: - support both configs - stop adding features to the old one - leave it to bake for a while - delete the old one in a year or two after putting a warning in the NixOS module that extraConfig is b&, and a proper deprecation cycle and migration
jade added this to the v2.91 milestone 2024-04-02 15:24:27 +00:00
Member

By config file do you mean nix.conf?

By config file do you mean `nix.conf`?
Owner

that and machines, which is a truly horrid format. there's no reason except original developer laziness that this file is a whitespace-separated record list

that and `machines`, which is a truly horrid format. there's no reason except original developer laziness that this file is a whitespace-separated record list
Member

Yeah, I'm really not a fan of the machines file format

Yeah, I'm *really* not a fan of the `machines` file format
jade added the
ux
label 2024-04-06 04:49:28 +00:00
jade modified the milestone from v2.91 to post-release 2024-08-13 01:19:36 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#209
No description provided.