Tim Cuthbertson

Ah I see. In that case `none` is a superset of `resolve`, which means there's no real reason to have a separate `resolve`? The "undoing" of earlier optimisations feels like...

If it could stop hiding type errors, then yeah that sounds like a good solution. In practice `DHALL_SHARED` is going to be a longer path so not something I'd want...

Glad to hear you're in agreement, and my apologies for being flippant. I do stand by my conclusion though, that most people (in ruby) won't realise that they need to...

Definitely :+1: on the docs. I'm not quite sure what you mean about the lazy collections, though. Everything is lazy currently, right? So I'd imagine you could call `.getSomeCollection()` without...

For context, it's OK if `esy` requires access to the network and local cache at _resolve_ time. In opam2nix (and most similar projects), there's two steps: 1. impurely, and with...

> What's missing to produce esy2nix from here? Funny you should ask! It turns out, [a very large amount of code](https://github.com/timbertson/fetlock) 😉 This is _super_ experimental, and not building it...

oops, it was still set to private (public now). It's definitely not something I'd support any time soon, but you're welcome to give it a try

Yep, looks like it's now being called with a single argument. `kwargs` is empty, while `args` is: ``` args=[dbus.Dictionary( { dbus.String(u'package-id'): dbus.String(u'git;2.1.0-2.fc21;x86_64;fedora', variant_level=1), dbus.String(u'description'): dbus.String(u'Git is a fast, scalable, distributed...

I don't think so - in this case I'd like to: - include everything under `res/` (recursively) - follow symlinks in this traversal - drop the `res` from the destination...

Ahh, I see. That does make it tricky. Couldn't you assume that if someone references `${lib:foo:bar}` then `foo` needs to be located, but not go any further than that? In...