[dev] Dropping tcsh support for Mac (all?) / changing configure's default
Hi *, because of 105003, own bad experience with tcsh (random build freezes, slow performance), encouraged by the kick4nt cws I'd like to go on and drop tcsh support at least for Mac OS X. dropping tcsh support means: changing configure's default to bash and issue a warning (or error) when tcsh is selected. The default login shell for Mac OS X is bash, so it definitely is available and it is proven to work without problems (Pavel builds with bash for years, so do I on all systems) So now to the reason why the d...@ooo list is adressed as well: Is somebody opposing chaning the default to bash for all systems? I.e. is there anybody who can give a reason why the default should stick with tcsh (be it for non-Mac or even all)? ciao Christian - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Dropping tcsh support for Mac (all?) / changing configure's default
Hi, On Fri, Sep 25, 2009 at 01:42:25PM +0200, Christian Lohmaier wrote: because of 105003, own bad experience with tcsh (random build freezes, slow performance), encouraged by the kick4nt cws I'd like to go on and drop tcsh support at least for Mac OS X. dropping tcsh support means: changing configure's default to bash and issue a warning (or error) when tcsh is selected. Yeah. The default login shell for Mac OS X is bash, so it definitely is available and it is proven to work without problems (Pavel builds with bash for years, so do I on all systems) So now to the reason why the d...@ooo list is adressed as well: Is somebody opposing chaning the default to bash for all systems? No. But a suggestion. But what about defaulting to the current login shell? People who might want tcsh already might use it as login shell Grüße/Regards, Rene - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Dropping tcsh support for Mac (all?) / changing configure's default
Stephan Bergmann wrote: But what about defaulting to the current login shell? People who might want tcsh already might use it as login shell I would vote for getting rid of tcsh-support in the build environment completely, sooner or later. Making the shell used within the build default to bash is a move in that direction, while making it depend on $SHELL is not. I wholeheartedly agree with Stephan. tcsh sucks large rocks, e.g. when it comes to output redirection; and the build system is complex enough supporting _one_ shell already ... Cheers, -- Thorsten signature.asc Description: Digital signature
Re: [dev] Dropping tcsh support for Mac (all?) / changing configure's default
Hi, On Fri, Sep 25, 2009 at 02:01:34PM +0200, Stephan Bergmann wrote: On 09/25/09 13:49, Rene Engelhard wrote: But what about defaulting to the current login shell? People who might want tcsh already might use it as login shell I would vote for getting rid of tcsh-support in the build environment completely, sooner or later. Making the shell used within the build default to bash is a move in that direction, while making it depend on $SHELL is not. True. But using $SHELL has the benefit that we can still get rid of the configure check at all and if we switched to bash we can just silently do it because no one will expect anything else because he's specifying --with-use-shell= (which IMHO was a bad idea to b egin withg, but at that time we had various shells, including 4nt...) Grüße/Regards, Rene - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Dropping tcsh support for Mac (all?) / changing configure's default
Hi, Le 25 sept. 09 à 13:42, Christian Lohmaier a écrit : The default login shell for Mac OS X is bash, so it definitely is available and it is proven to work without problems (Pavel builds with bash for years, so do I on all systems) FYI there were other people building OOo on Mac OS X before you :-) And yes, the tcsh was a nightmare. +1 for dropping tcsh support, at least on Mac OS X ( IIRC, only Mac OS X is concerned, isn't it ?) Eric -- qɔᴉɹə
Re: [dev] Dropping tcsh support for Mac (all?) / changing configure's default
Thorsten Behrens wrote: Stephan Bergmann wrote: But what about defaulting to the current login shell? People who might want tcsh already might use it as login shell I would vote for getting rid of tcsh-support in the build environment completely, sooner or later. Making the shell used within the build default to bash is a move in that direction, while making it depend on $SHELL is not. I wholeheartedly agree with Stephan. tcsh sucks large rocks, e.g. when it comes to output redirection; and the build system is complex enough supporting _one_ shell already ... Yes, if possible (means: if no platform is know where using bash is not possible) let's drop tcsh support. But if we don't do it: please at least let configure always generate just one shell script, not always both of them. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to nospamfor...@gmx.de. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
