Date: Fri, 19 Nov 2010 15:32:16 +0000 (UTC) From: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-ports@freebsd.org Subject: Re: Mk/bsd.command.mk: missing CSH tag Message-ID: <ic65a0$16m1$1@lorvorc.mips.inka.de> References: <4CE5280E.3090009@zedat.fu-berlin.de> <AANLkTinmZ2YXxMAPjghtur3n2GT-N16d0FFAc0=khb=k@mail.gmail.com> <86wro9e6e4.fsf@gmail.com> <AANLkTinip-y9n2w=bJ7QKidymYTQSsmSiybxU7FWoY==@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eir Nym <eirnym@gmail.com> wrote: > >>> Since when? If you are missing /bin/csh, your system is defective > >>> or at least nonstandard. > >> > >> It is good joke, thanks > > > > I guess he's talking about the ports tree being too fragile for some > > non-default configurations and not many people are willing to fix it. > > I understand this. Port can check this (because it is optional system > component) and use another or generate error. This is very confusing. One of us is out of sync with reality. (If it's me, I'd like to know.) Your confident claim that csh is optional is like stating that the sky is green and the sun is purple. Did I miss something? Yes, I know there is a WITHOUT_TCSH knob. You can use this when you build a FreeBSD-based embedded system where you know you won't need csh. In no way does the existence of this knob imply that csh is optional on a standard FreeBSD system where you build ports. -- Christian "naddy" Weisgerber naddy@mips.inka.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ic65a0$16m1$1>