Ideas for Remote Justfiles

Your [Remote Justfiles](https://just.systems/man/en/remote-justfiles.html) capability is underwhelming. A real solution would make Just much more appealing to companies which want to provide base-recipes centrally! This should strongly suggest using a rigorously adhered to server side versioning scheme! Just downloading a URL whose content can change randomly is chaos! Of course HTTP gives no guarantees for this, but a documented intention is better than nothing. If there is some server-protocol that gives cargo-, npm-, maven-like overwrite-safe versioned download, that would be great! Your two-step suggestion is inconvenient. Gnumake solves this by building and (re-)reading an include file. Difficult to imitate, since Just recipes are all `.PHONY`. Maybe you could have a `[non_phony]` (to be bikeshedded) attribute for such rare cases, where the recipe name or attribute parameter is the name of the produced file. If `import` takes a string as parameter, why can it not be a backtick string? This would be a one-pass equivalent: ````just import ``` foo=foo.just compare= [ -e $foo ] && compare="-z $foo" curl -s $compare -o $foo https://raw.githubusercontent.com/casey/just/master/justfile-v1.0.0 echo $foo ``` ```` Actually this is still very cumbersome! It would be much cooler, if that were the behaviour for some syntax variant of ```just import 'foo.just' @ 'https://raw.githubusercontent.com/casey/just/master/justfile-v1.0.0' ``` It would use builtin reqwest or ureq via rustls, if activated by feature, else fall back to the first found external curl, wget…