Re: Intentionally bad port behaviour

[Chris]

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. */

 |         /* (We are killing the user, obviously.) */
 |

 |          * find out what are we doing... ;-) --pasky */
 |         /* TODO: Be more cruel when in trouble? ;-) --pasky */
 |

 |                 "You will _suffer_ >:).\n"
 |                 "\n"
 |                 "CPU burning sequence initiated...\n", f);
 |
 |         /* TODO: Include cpuburn.c here. --pasky */
 |         while (1);

Cheers

| /* 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. */ | /* TODO: Gettextify? Er, better not. More people (translators) could | 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"

Exceptionally bad behavior for anything in the ports tree.
I think this port should be patched out of the ports tree.

--Chris

0xBDE49540.asc
Description: application/pgp-keys