-
Notifications
You must be signed in to change notification settings - Fork 115
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
Implement builtins.path #128
Comments
This could be challenging, since I think these "enriched paths" are supposed to be interchangeable with other paths. |
nix actually handles this by figuring out the store path and using that as a plain path object. There are no actual 'enriched path objects' in nix libexpr. |
Actually now that i check more closely, builtins.path returns a string, not a path! |
Right:
|
I started looking into this today. Haven't made much progress, but I'm getting more familiar with the codebase. Will try again tomorrow. |
Great! Once this is closed we’ll be able to turn on the full language tests for Travis! |
@jglukasik Definitely ask for some help from someone on this tomorrow. @shlevy will have all the knowledge you need on the nix side of things. It would be great to get this one finished this weekend. |
After some discussion with @mightybyte , we've realized this might be a bit too large of a first change for me. I'll let someone else tackle this. |
I'm going to work on this on the plane tomorrow. |
@jwiegley This requires nar serialization, which @imalsogreg is working on |
I realized that soon after looking into it, so I’m going to hold off and leave you guys to it. |
@shlevy since were not reimplementing the store, what are you think about binding to libstore through the FFI? |
We could also shell out as I did for derivationStrict; it's dirty, but if it's easier it might be worth it since we should eventually try not to have a dependency at all. |
I’m fine with shelling out right now, since it would let us move on to other problems. |
Eh, libnixstore isn't really stable at all and is not a nice interface at all. Not sure why we'd prefer that to implementing the daemon protocol. |
@shlevy Do you think it makes sense to shell out in the immediate future to get this working, and then use the daemon protocol as the next step? |
If that gets us something useful, sure. First step of the required logic to do readonly mode properly (so no need to talk to the daemon) is up at haskell-nix/hnix-store#7 |
This Builtin should be added here.
This doesn't have a
.exp
file; I think that means it just needs to evaluate without error.Fixes
eval-okay-path
(remove it fromnewFailingTests
list).The text was updated successfully, but these errors were encountered: