Closed Baughn closed 7 years ago
It is indeed the hash which is throwing it off. I'm not even sure what #~1.2
is supposed to mean. In this case I suggest tweaking the generated nix until a solution can be found.
It seems to mean.. "Look for GitHub releases matching this version, approximately; install that."
It seems to work if we use the source specifier and the resolved version, e.g. components/bootstrap#3.3
. Without the source specifier (e.g. just 3.3
) I ran into trouble because it looked in the wrong place.
I've added my workaround in https://github.com/rvl/bower2nix/pull/6
Thanks @johbo, workarounds are good. I will check & merge later.
Fixed by 16521d4f502145f6bcaaff992aa13e251f39a930, sorry for the delay.
E.g. for a bower.json such as this:
...the generated .nix file will include ~ in the version number:
Not only does this break bowerVersion, but it would also make the fetch non-fixed in the event that bowerVersion were fixed.
You do handle ~-ranges correctly in other cases; at the moment, I suspect it's the hash that's throwing it off.