Re: [dev] drop tcsh support?
On 01/11/10 19:40, Konstantin Tokarev wrote: Yes, in FreeBSD it's /usr/local/bin/bash (but there's /bin/sh if POSIX shell is enough) And there is no /bin/bash (which would probably be a link to /usr/local/bin/bash)? Just to be sure... -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] drop tcsh support?
Hi Stephan From: Stephan Bergmann stephan.bergm...@sun.com Subject: Re: [dev] drop tcsh support? Date: Tue, 12 Jan 2010 09:41:44 +0100 On 01/11/10 19:40, Konstantin Tokarev wrote: Yes, in FreeBSD it's /usr/local/bin/bash (but there's /bin/sh if POSIX shell is enough) And there is no /bin/bash (which would probably be a link to /usr/local/bin/bash)? Just to be sure... No /bin/bash. Thanks, -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] drop tcsh support?
On 01/11/10 20:17, Christian Lohmaier wrote: Regarding POSIX: I already did bash-builds with the POSIXLY_CORRECT environment variable - no problem at all. (so /bin/sh could be used as a fallback, possibly with an appropriate configure-warning-message) My understanding is that bash posix mode merely chane[s] the behavior of bash where the default operation differs from the POSIX 1003.2 standard [quoting from the man page], but does not forbid bash extensions (like here strings, or () process substitution). -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] drop tcsh support?
On 01/12/10 09:44, Maho NAKATA wrote: On 01/11/10 19:40, Konstantin Tokarev wrote: Yes, in FreeBSD it's /usr/local/bin/bash (but there's /bin/sh if POSIX shell is enough) And there is no /bin/bash (which would probably be a link to /usr/local/bin/bash)? Just to be sure... No /bin/bash. OK, so we will have to keep the logic in configure to find the bash pathname, and transport that to solenv/inc/startup/startup.mk. Thanks, -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] drop tcsh support?
From: Stephan Bergmann stephan.bergm...@sun.com Subject: Re: [dev] drop tcsh support? Date: Tue, 12 Jan 2010 09:49:03 +0100 On 01/12/10 09:44, Maho NAKATA wrote: On 01/11/10 19:40, Konstantin Tokarev wrote: Yes, in FreeBSD it's /usr/local/bin/bash (but there's /bin/sh if POSIX shell is enough) And there is no /bin/bash (which would probably be a link to /usr/local/bin/bash)? Just to be sure... No /bin/bash. OK, so we will have to keep the logic in configure to find the bash pathname, and transport that to solenv/inc/startup/startup.mk. Thanks! Just a note. I succesfully compiled with --with-use-bash=bash on FreeBSD 8.0-RELEASE-p2 please see the diff - http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice.org-3-devel/Makefile.diff?r1=1.458;r2=1.459 . -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] drop tcsh support?
Two questions remain: For one, the to-be-sourced scripts currently ensure that USE_SHELL's path is in PATH, but I see no reason for that? For another, are there any relevant configurations where bash is not at /bin/bash? Yes, in FreeBSD it's /usr/local/bin/bash (but there's /bin/sh if POSIX shell is enough) -- Regards, Konstantin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] drop tcsh support?
On Mon, Jan 11, 2010 at 4:19 PM, Stephan Bergmann stephan.bergm...@sun.com wrote: Any objections against dropping support for using tcsh as the shell invoked by dmake within the OOo code base? We had that discussion lately and the results were: No objections. At least nobody did complain/wanted to keep tcsh. In fact I already planned to do a related cws after the 3.2 release (but of course I won't object if somebody else wants to do it) [...] Two questions remain: For one, the to-be-sourced scripts currently ensure that USE_SHELL's path is in PATH, but I see no reason for that? Me neither. If the full path is given anyway... If at all: configure's job, not the one of the env-script. For another, are there any relevant configurations where bash is not at /bin/bash? I don't know any (but that doesn't count much I guess :-) Regarding POSIX: I already did bash-builds with the POSIXLY_CORRECT environment variable - no problem at all. (so /bin/sh could be used as a fallback, possibly with an appropriate configure-warning-message) ciao Christian - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
