You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, one problem that marsnix has is that it only provides inputs for one specific nixpkgs revision.
This means that one might run into trouble when building outputs which are based on any other nixpkgs revision.
It would be great if marsnix could provide all inputs for all nixpkgs revisions that have been released during a certain time period, like for example everything between nixos-22.05 and master.
For example, the user could specify a minimum nixpkgs revision, so that marsnix would evaluate and download all inputs of all nixpkgs revisions that have been created after that minimum revision.
At first glance that sounds expensive, but maybe really isn't that bad. Since hydra doesn't evaluate every single nixpkgs revision, marsnix doesn't need to as well. Hydra only evaluates nixpkgs several times a day. Marsnix just needs to get the list of revisions from hydra, and evaluate exactly those revisions.
Still this might result in around 1000 revisions to evaluate for the time frame of one year, but the good thing is that the result of evaluating a revision can be cached forever. Therefore the computation cost only has to be paid once, when the user activates the marsnix service for the first time.
The text was updated successfully, but these errors were encountered:
Currently, one problem that marsnix has is that it only provides inputs for one specific nixpkgs revision.
This means that one might run into trouble when building outputs which are based on any other nixpkgs revision.
It would be great if marsnix could provide all inputs for all nixpkgs revisions that have been released during a certain time period, like for example everything between nixos-22.05 and master.
For example, the user could specify a
minimum
nixpkgs revision, so that marsnix would evaluate and download all inputs of all nixpkgs revisions that have been created after thatminimum revision
.At first glance that sounds expensive, but maybe really isn't that bad. Since hydra doesn't evaluate every single nixpkgs revision, marsnix doesn't need to as well. Hydra only evaluates nixpkgs several times a day. Marsnix just needs to get the list of revisions from hydra, and evaluate exactly those revisions.
Still this might result in around 1000 revisions to evaluate for the time frame of one year, but the good thing is that the result of evaluating a revision can be cached forever. Therefore the computation cost only has to be paid once, when the user activates the marsnix service for the first time.
The text was updated successfully, but these errors were encountered: