Goal of this repository
Closed this issue · 1 comments
This repository is meant to be used with the future Zilch package manager.
The goal is to reproduce how nixpkgs using a common configuration language (such as Dhall, Nix, etc).
These details will need to be fixed later, when work on the package manager begins:
- what language for the configuration?
- how to create dependencies between packages?
- nixpkgs uses a complex build system to pre-build everything; do we also need this?
- will this repository grow too much that it won't be easily clonable?
- what about potential contributors?
- which license to choose for such repository? MIT, BSD3, the more restrictive GPL or any other?
Please note that it will not accept any sort of code other than the configuration, to keep things as light as possible.
- what language for the configuration?
Dhall will be used (despite lacking recursion and being strict, package fetching is not done here).
- how to create dependencies between packages?
This will not be handled in the package set, but rather on an individual basis in each project's configuration.
Those will be handled completely by the project manager.
- nixpkgs uses a complex build system to pre-build everything; do we also need this?
We could have one to validate (the package is definitely a Zilch package, and at least compiles with the current GZC version of the package set) any package that is contributed here, but this is not necessary at the moment.
- will this repository grow too much that it won't be easily clonable?
Hopefully not, as it only contains Dhall text files.
- what about potential contributors?
A contributing guide will be written to know how to include a new package here.
- which license to choose for such repository? MIT, BSD3, the more restrictive GPL or any other?
Most probably the MIT one, because it is not restrictive at all.
There may be only some problems with AGLP-licensed packages, but this will be seen when needed.