Nixify software with less effort [maintainer=@DavHau]
Go to file
2021-10-06 00:01:26 +09:00
docs finalize new CLI 2021-10-05 12:25:39 +07:00
notes fix node2nix builder 2021-09-22 00:30:56 +01:00
specifications add templates for adding translators 2021-09-23 11:05:25 +01:00
src yarn.lock: initial translator 2021-10-06 00:01:26 +09:00
.gitignore implement UI and examples: 2021-09-09 23:42:56 +02:00
flake.lock translators: add yarn.lock 2021-10-05 20:52:00 +09:00
flake.nix translators: add yarn.lock 2021-10-05 20:52:00 +09:00
LICENSE Initial commit 2021-09-03 17:30:52 +02:00
README.md docs: minor readme improvements 2021-09-30 01:35:46 +01:00

[WIP] dream2nix - A generic framework for 2nix tools

dream2nix is a generic framework for 2nix converters (converting from other build systems to nix).
It focuses on the following aspects:

  • Modularity
  • Customizability
  • Maintainability
  • Nixpkgs Compatibility (not enforcing IFD)
  • Code de-duplication across 2nix converters
  • Code de-duplication in nixpkgs
  • Risk free opt-in FOD fetching (no reproducibility issues)
  • Common UI across 2nix converters
  • Reduce effort to develop new 2nix solutions
  • Exploration and adoption of new nix features
  • Simplified updating of packages

Motivation

2nix converters, or in other words, tools converting instructions of other build systems to nix build instructions, are an important part of the nix/nixos ecosystem. These converters make packaging workflows easier and often allow to manage complexity that would be hard or impossible to manage without.

Yet the current landscape of 2nix converters has certain weaknesses. Existing 2nix converters are very monolithic. Authors of these converters are often motivated by some specific use case and therefore the individual approaches are strongly biased and not flexible. All existing converters have quite different user interfaces, use different strategies of parsing, resolving, fetching and building while providing significantly different options for customizability. As a user of such converter it often feels like there is some part of it that suits the needs well, but at the same time it has undesirable hard coded behaviour. Often one would like to use some aspect of one converter combined with some aspect of another converter. One converter might do a good job in parsing a specific lock file format, but lacks customizability for building, while another one provides a good customization interface, but is unable to parse the lock file format. Some converters are restricted to use IFD or FOD, while others enforce code generation.

The idea of this project is to create a standardized, generic, modular framework for 2nix solutions, aiming for better flexibility, maintainability and usability.

The intention is to integrate many existing 2nix converters into this framework, thereby improving many of the previously named aspects and providing a unified UI for all 2nix solutions.

Further Reading