> Because the code is so old we don't want to have an intern figure out how to do it. (Adding a switch for a new PCRE, such as /P, is hard) Oh, and reading and

> Because the code is so old we don't want to have an intern figure out how to do it. (Adding a switch for a new PCRE, such as /P, is hard) Oh, and reading and understanding licenses is HARD?!?!? WTF? The problem isn't reading and understanding the license: the problem is that you now have to provide security updates in a timely manner for code you don't know. (And relying on upstream alone here doesn't work: you might have a stability policy which means you only want to ship security fixes and not other changes, so you have to be able to separate them out and deal with the conflicts while not knowing the code.)