Essien Ita Essien writes:
>Alessio 'mOLOk' Bolognino wrote:
>>
>> PKGBUILDs are bash scripts, what does build("mysql") mean in bash
>> scripting?
>
>PKGBUILDs don't _have_ to remain bash scripts... as long as we don't
>expect users to do a ./PKGBUILD just to build a package.
>
>One of the things i've learnt is that the _user_ interface should be
>allowed to be awkward, just to keep the implementors work down to a
>minimum. Also parsing of simple formats like this are actually a plus
>(depends on who's thinking of it though). I think, if we keep limiting
>it to bash scripting idioms we'll be neglecting the reality infront of
>us which is that a PKGBUILD is _not_ _actually_ a bash script, its a
>_makepkg_ script :)
It seems to me that you do not understand the KISS philosophy.
You have not made a case that bash is not up to the job, but even
if bash were not up to the job, before resorting to defining a
new language (the makepkg script), a person should try to replace
bash with another _existing_ language. (Python, say.)
Unix and Linux already have too many little languages.
_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch
