Is it possible to ask upstream for a tag?

Done!

@GrahamcOfBorg build liquidprompt

@GrahamcOfBorg build liquidprompt

It would also be interesting to install the default configuration and theme files. They would serve as examples for the user willing to change configuration and theming.

As liquidprompt needs to be sourced instead of executed (see missing executable bit) this file definitly does not belong into $out/bin.

What files would you add to the package and where? Personally, I don't really see the advantages of putting default configs into the package as the majority will define their own config. And if you need a reference, you will be better of with reading the README of liquidprompt.

According to https://superuser.com/questions/176783/what-is-the-difference-between-executing-a-bash-script-vs-sourcing-it both execution and sourcing of a bash shell script uses PATH to find the script file. The difference is only in the environment used: execution creates a new environment, which is discarded when the script finishes, and sourcing does not create one, running the script in the same process which sourced it.

It is desirable that the script be placed in a directory in PATH, making it easier to be found when sourced.

Currently I am sourcing it with something like

. /nix/store/nbxjwa5vz6vgvwhxjvn909am5ly9payw-liquidprompt-unstable-2018-05-21/share/bash/plugins/liquidprompt/liquidprompt

which is not very user friendly and will change in the next rebuild if the source or any dependency changes.

If it can be found in PATH, it could be just:

. liquidprompt

It does not need to be executable, though. That would be enough to prevent it from being executed instead of sourced.

Other distributions like Arch (AUR) installs it at /usr/bin.

I would install liquidpromptrc-dist and liquid.theme to $out/share/doc. Maybe README.md and demo.png too.