A modular framework for automated, reproducible Nix packaging across multiple programming language ecosystems.
dream2nix is a framework for automated Nix packaging that simplifies creating reproducible packages for various programming language ecosystems. It provides a standardized approach to packaging that reduces duplication of effort across different language-specific solutions. The framework aims to improve flexibility, maintainability, and usability of Nix packaging workflows.
Nix users and maintainers who need to package software from multiple programming language ecosystems, and developers creating or maintaining language-specific packaging solutions for Nix.
dream2nix offers a modular framework that unifies packaging approaches across different languages, reducing code duplication and maintenance burden while providing a consistent user experience. It enables exploration of new Nix features and simplifies package updates through its standardized architecture.
Simplified nix packaging for various programming language ecosystems [maintainer=@DavHau]
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built with reusable components for different packaging tasks, enabling flexible and customizable workflows that adapt to specific needs, as highlighted in the modular design goals.
Automates packaging for various programming language ecosystems, reducing duplication and providing a unified approach, which is core to its value proposition.
Shared logic across different 2nix solutions minimizes maintenance burden, aligning with the goal to reduce effort and improve maintainability.
Offers a consistent interface across all supported languages, simplifying packaging workflows and enhancing usability, as stated in the framework's aims.
The README explicitly warns that APIs are under development and changes will break setups, making it unreliable for stable or production environments.
Not all features and subsystems are migrated to the new drv-parts architecture, requiring users to rely on a legacy branch for some functionalities, adding complexity.
Requires deep understanding of both Nix and the framework's modular system, which can be daunting for users new to automated packaging or Nix in general.