hpkgs
hpkgs copied to clipboard
andrewchambers
Repository configuration
I think we should consider a configuration file for the hpkgs repo, some things to consider:
- Debug symbols + source code.
- Man pages.
- Filters.
My overall plan is to divide hpkgs into several quality tiers, and for a package to qualify for the highest tiers, it must respect all configuration.
In practice this may mean we don't do the nix thing of multiple package outputs, instead opting for different configurations where you rebuild.
(I'm not sure if this is a good place to write it, but I have no better idea for a place ATM: I'm having some loose thoughts related to some kind of "staged/phased builds". Kinda making me thing of Docker where each "command" creates a new filesystem layer; I am thinking specifically of potential reuse of artifacts between various phases of a build, e.g. when working on a new package. This also feels like it could be helpful to avoid repeated work here in this very issue (#77). At the same time I fully understand this is not a perfect solution, e.g. in Docker the layers often get invalidated if something changes in an earlier layer. Full reuse would probably kinda require also using some Git-like filesystem where each separate file is also dedupped by hash. Those are very vague thoughts for now, thus I'm putting this whole stream-of-consciousness in parentheses, with the intention that if any idea from here sparks anything in you, that's awesome; if not, then not much lost I guess.)
