On 19 November 2010 20:47, Anonymous <[email protected]> wrote:
> Eir Nym <[email protected]> writes:
>
>> On 19 November 2010 18:32, Christian Weisgerber <[email protected]> wrote:
>>> Eir Nym <[email protected]> wrote:
>>>
>>>> >>> Since when? If you are missing /bin/csh, your system is defective
>>> 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.
>
> What are those requirements that constitute standard FreeBSD system
> capable of building ports?
>
>>>
>>
>> Ok, another example is NIS. You can turn off NIS support in your
>> system, and ports will check NIS biraries if they need them.
>
> There are more examples
>
> - openssl: WITH_OPENSSL_PORT
> - pkg_install: .if exists(...)
> - fetch: .if exists(...)
> - texinfo: by relying on PATH
>
> And rather than resurrecting shells/tcsh one can also also try
>
> BUILD_DEPENDS += ${CSH}:${PORTSDIR}/shells/44bsd-csh
>
> .if exists(/bin/csh)
> CSH ?= /bin/csh
> .else
> CSH ?= ${LOCALBASE}/bin/44bsd-csh
> .endif
>
> But some ports may assume csh is tcsh like sh is bash on linux.
>
Oh, sorry, I haven't knew if csh is in ports tree. thanks
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
