I'm not sure how big an ask this is, but it would be great if fish were relocatable (as in, once built, it could be moved and run from any directory as long as all the files moved in unison).
Personally I'd like to create a zeroinstall feed for fish, so that I can run it on whatever machine I find myself on without requiring admin priviledges or build tools. The only thing preventing that right now is the lack of relocatability of the build result. This would obviously be useful for more that just 0install - e.g you could also take it with you on a USB stick.
I'm not really sure how hard it would be, but in general it should usually be possible to either construct relative paths (relative to the fish executable), or to use environment variables (perhaps $FISH_ROOT).
One more restriction on 0install implementations is that once unpacked, they must remain readonly. I presume that wouldn't be a problem (config goes under ~/.config), but I thought I'd mention it just in case.
I'm not sure how big an ask this is, but it would be great if fish were relocatable (as in, once built, it could be moved and run from any directory as long as all the files moved in unison).
Personally I'd like to create a zeroinstall feed for fish, so that I can run it on whatever machine I find myself on without requiring admin priviledges or build tools. The only thing preventing that right now is the lack of relocatability of the build result. This would obviously be useful for more that just 0install - e.g you could also take it with you on a USB stick.
I'm not really sure how hard it would be, but in general it should usually be possible to either construct relative paths (relative to the
fishexecutable), or to use environment variables (perhaps $FISH_ROOT).One more restriction on 0install implementations is that once unpacked, they must remain readonly. I presume that wouldn't be a problem (config goes under ~/.config), but I thought I'd mention it just in case.