Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sources.nix: Use the fetcher instead of creating derivations #32

Closed
wants to merge 2 commits into from

Conversation

nlewo
Copy link
Collaborator

@nlewo nlewo commented Mar 12, 2019

The created derivations were not enough well created to be handled by
Hydra as a package [1]. Basically, Hydra recurses on the provided
attribute set to figure out which attribute is a derivation. If an
attribute set contains an attribut type="derivation", it is consider
as a derivation. But Hydra requires also more attributes such as a
name, system...

Since we are now using fetchers from nixpkgs, we can directly use
them since they return a derviation.

[1] I add all Niv derivations as packages in Hydra in order to copy
them to the binary cache since it is no done at evaluation time.

@nlewo
Copy link
Collaborator Author

nlewo commented Mar 13, 2019

JSON attributes are exposed in the niv attribute set inside the derivation to avoid name collision on the type attribute for instance. Note this is a breaking change since JSON attributes were in the derivation attribute set directly.

@nlewo nlewo force-pushed the no-longer-manual-derivation branch from dbeedac to 6ae7f5c Compare March 13, 2019 18:42
nlewo added 2 commits March 13, 2019 19:42
The created derivations were not enough well created to be handled by
Hydra as a package [1]. Basically, Hydra recurses on the provided
attribute set to figure out which attribute is a derivation. If an
attribute set contains an attribut `type="derivation"`, it is consider
as a derivation. But Hydra requires also more attributes such as a
`name`, `system`...

Since we are now using fetchers from `nixpkgs`, we can directly use
them since they return a derviation.

[1] I add all Niv derivations as packages in Hydra in order to copy
them to the binary cache since it is no done at evaluation time.
This `niv` attribute set contains all JSON attributes.

JSON attributes are exposed in the `niv` attribute set inside the
derivation to avoid name collision on the `type` attribute for
instance. Note this is a breaking change since JSON attributes were in
the derivation attribute set directly.
@nlewo nlewo force-pushed the no-longer-manual-derivation branch from 6ae7f5c to 7243969 Compare March 13, 2019 18:43
@nlewo
Copy link
Collaborator Author

nlewo commented Mar 28, 2019

I close it to avoid breaking backward compatibility.
Also, I can make Hydra happy by using the outPath attribute which is a valid derivation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant