In message <599da64a-e321-fb15-f44f-9088c9f30...@radscan.com>, Jon Trulson writ es: > On 3/26/21 12:19 PM, Brent Busby wrote: > > Zeke Williams <lakele...@gmail.com> writes: > > > >> I already have ksh installed under /bin in my distro. I had to > >> download from github ksh93 because the sourceforge git didn't come > >> with it and the patch as part of compilation failed to apply to be > >> able to compile it and resulted with an error. Is there anything > >> mandatory that ksh93 does for CDE? Can we remove it and just have the > >> already installed ksh do the work instead? > > Not to take away from your question (which is a good one), I have a > > related question which may have an answer similar or related to whatever > > the answer is to yours: > > > > When you compile CDE through the FreeBSD ports system, it pulls in ksh93 > > as a dependency package. There is a package options switch for the > > ksh93 package to let you choose whether the port will install as 'ksh' > > or 'ksh93'. Last time I tried to install CDE this way, the CDE build > > failed if ksh93 was installed as 'ksh' because it couldn't be found. I > > really prefer installing as ksh since ksh93 is kind of bizarre as an > > executable name, and the FreeBSD port gives you a choice to let you > > avoid that. > > > > Will CDE on FreeBSD always require ksh to be named ksh93 at compile time? > > It does right now because there were various forks of ksh that are > broken or incompatible. > > This is defined in the config/cf/FreeBSD.cf file I think.
It's defined in all the cf files. slippy$ ag -s KornShell config config/cf/FreeBSD.cf 54:#undef KornShell 55:#define KornShell /usr/local/bin/ksh93 config/cf/Imake.tmpl 185:#ifndef KornShell 186:#define KornShell /bin/ksh 188:#ifndef DtKornShell 189:#define DtKornShell /usr/dt/bin/dtksh 909: KORNSHELL = KornShell 910: DTKORNSHELL = DtKornShell config/cf/OpenBSD.cf 1077:#ifndef KornShell 1078:#define KornShell /usr/local/bin/ksh93 1081:#ifndef DtKornShell 1082:#define DtKornShell /usr/local/dt/bin/dtksh config/cf/NetBSD.cf 316:#ifndef KornShell 317:#define KornShell /usr/pkg/bin/ksh93 config/cf/README 95: KornShell command used to run Korn Shell slippy$ > > This is one of those 'janitorial' problems that would be nice to solve - > the need to have a ksh installed in order to build CDE. > > I think this requirement could be removed -- there are a variety of > scripts used during a CDE build using ksh > > But - some of those script (I believe) require ksh/posix features. So, > one would need to go through these scripts and port them if required. I > think /bin/bash would be preferable as most people have that or can > easily install it. Or even the default /bin/sh, if that can be made to > work. Last time I looked this was correct. bash and ksh handle arrays differently and is one reason Oracle install scripts require ksh on Solaris and Linux. Ideally you should be able to make it work with Bourne. The commercial systems (AIX, Solaris, and many others I worked on that no longer exist) all had ksh. Linux distros come with bash. The BSDs (FreeBSD here) does not because bash is GPL and we at FreeBSD want to keep the base system free of GPL; people need to install the shell of their choice. Having said that, in FreeBSD pkg automatically installs prerequisites and the ports system will drag them in for build. In that regard it doesn't matter unless people want to keep their systems as lean as possible. Personally, I don't see ksh as a big roadblock. I don't mind it. > > Volunteers to tackle that would be welcome :) > > -jon -- Cheers, Cy Schubert <cy.schub...@cschubert.com> FreeBSD UNIX: <c...@freebsd.org> Web: https://FreeBSD.org NTP: <c...@nwtime.org> Web: https://nwtime.org The need of the many outweighs the greed of the few. _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
