2015-12-12 0:38 GMT+03:00 Bram Moolenaar <[email protected]>:
>
> Random wrote:
>
> > On 2015-12-11, Bram Moolenaar <[email protected]> wrote:
> > > Sorry, I just do not agree with that spec. Building software using
> > > environment variables is brittle and is bound to go wrong. Environment
> > > variables can be set for various reasons, and there is hardly any
> > > control over them. Generally they are user preferences.
> >
> > Every environment variable that is set is there for a reason
> > (*someone* had to put it there, after all). I don't understand
> > why you think there's going to be a user preference called
> > SOURCE_DATE_EPOCH. Users don't put random names in their
> > environment, they put names that actually mean something to
> > programs that they use.
> >
> > Also, "generally they are user preferences" is a bit of a
> > stretch. My environment in a new shell window right now
> > consists of the following variables:
> >
> > USER SHLVL OLDPWD XDG_SESSION_COOKIE LOGNAME TERM PATH LANG PWD
> > EDITOR HOME MAIL SHELL SSH_CLIENT SSH_CONNECTION SSH_TTY TMUX
> > TMUX_PANE VISUAL XDG_RUNTIME_DIR XDG_SESSION_ID _
> >
> > I think that of those, only VISUAL, EDITOR, and if you really
> > stretch the definition SHELL and PATH, are "user preferences".
>
> The name user preferences was not quite right, but you can see that
> these values will remain the same no matter what command you run. As
> soon as you have something like:
>
> setenv SOME_VAR=some_value
> run command
> setenv SOME_VAR=
>
> Then there is something wrong. In the case of SOURCE_DATE_EPOCH it's
> really passing a value to the command being run, and that is not right.
>
LANG=C run command
TZ=Europe/Jersey date
PYTHONPATH=. python …
DISTDIR=~/tmp/distfiles ebuild *.ebuild manifest
LD_LIBRARY_PATH=… run command
? It is not uncommon to use environment variables for one specific
command. Environment variables are usually used for passing values that are
unlikely to change, and in many cases may be mistaken with user settings.
>
> > The problem with using command line arguments is that not every
> > build system uses the same command.
>
> So just pass the right one. If you build a program there are lots of
> options you need to control anyway, this is just one of them.
>
> --
> A man is incomplete until he's married ... and then he's finished!
>
> /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net
> \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org
> ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" 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.
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" 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.
