>
> > go run github.com/fruit/banana arg1 arg2 ...
>
> I don't like the idea of giving go run any more powers. It is already
> being horribly abused.
>
I understand the sentiment; it needn't be the run sub-command of course...
it's about adding this behaviour to the go command.
> Your users can perhaps try
>
> $ $GOPATH/bin/banana arg1 arg2
>
> if properly setting PATH is beyond whatever.
>
This doesn't work when GOPATH contains multiple values... and doesn't deal
with the name clash in the various "${GOPATH//://bin:}/bin" directories.
On *nix, many users have $HOME/bin already in $PATH, so using (my setup)
> export GOPATH=$HOME in .bashrc/.profile solves everything.
>
This is another option, sure.
But I guess this is the point; based on your setup, environment, level of
proficiency... there are so many options/permutations.
The idea here is to acknowledge all of them and provide an option that will
"just work" in all scenarios, a mode which the user can simply ignore if
they know their environment is setup in "the right way"
Paul
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
