On 05/04/2011 13:04, Michael Stahl wrote:
hi all,
currently configure generates 2 shell scripts for the environment,
one for Bourne shell and one for tcsh.
the tcsh file is known to ... annoy people.
would anybody complain if the tcsh file were gone?
since there are apparently no tcsh
On 08.04.2011 14:22, Christian Lohmaier wrote:
On Thu, Apr 7, 2011 at 9:47 AM, Mathias Bauernospamfor...@gmx.de wrote:
Hi,
AFAIK tcsh doesn't work anymore anyway -
using tcsh as the shell used *by* the build: yes.
But the environment files are for the user's shell, and there it would
still
Hi,
AFAIK tcsh doesn't work anymore anyway - at least it's not supported
anymore. I think that the only reason that we still create two scripts
is that nobody was annoyed enough to remove the code doing this. :-)
Months ago I worked on that but then got in serious merge conflicts as
On Thu, Apr 7, 2011 at 9:47 AM, Mathias Bauer nospamfor...@gmx.de wrote:
Hi,
AFAIK tcsh doesn't work anymore anyway -
using tcsh as the shell used *by* the build: yes.
But the environment files are for the user's shell, and there it would
still work.
Months ago I worked on that but then got
I guess it shouldn't make a big difference for anyone whether he uses
bash or tcsh for building OOo, so killing tcsh support is fine, IMO.
Malte.
Michael Stahl wrote, On 05.04.2011 13:04:
hi all,
currently configure generates 2 shell scripts for the environment,
one for Bourne shell and
