Re: Intentionally bad port behaviour

On 2022-11-14 16:05, Jamie Landeg-Jones wrote:
> What's the policy on dodgy acting ports?
> 
> I had elinks crash (well, the spidermonkey part crashed)
> 
> elinks then accused me of editting the config file manually (I hadn't)
> and then went into an intentional endless loop.
> 
> I think this should be patched out:
> 
>  | src/util/error.c :
>  |
>  |         /* User torturation. */
>  |         /* You are worried about what you see here? You don't see 
> anything in
>  |          * the first place. Also, be assured that we know what are we 
> doing. */
>  |         /* (We are killing the user, obviously.) */
>  |
>  |         /* TODO: Gettextify? Er, better not. More people (translators) 
> could
>  |          * find out what are we doing... ;-) --pasky */
>  |         /* TODO: Be more cruel when in trouble? ;-) --pasky */
>  |
>  |         fputs(  "Wheeeeeeeeeee! You played with the config.h by hand, 
> didn't you?\n"
>  |                 "Of _COURSE_ you did! Is that how a nice .. creature 
> behaves like?\n"
>  |                 "Of _COURSE_ it isn't! I feel offended and thus I will 
> revenge now!\n"
>  |                 "You will _suffer_ >:).\n"
>  |                 "\n"
>  |                 "CPU burning sequence initiated...\n", f);
>  |
>  |         /* TODO: Include cpuburn.c here. --pasky */
>  |         while (1);
> 
> Cheers
Exceptionally bad behavior for anything in the ports tree.
I think this port should be patched out of the ports tree.

--Chris