Conversation
This is an attempt to make the code easier to follow and reuse pieces It isn't tested, and given it's a refactor, it wouldn't shock me if I messed up.
|
There's another concern: Exim is run on platforms which do not have POSIX sh and when I've made changes to the build scripts, I've dealt with bug-reports because of sensible things which just didn't work on some ancient platform or another. There's a strong difference between what a new project can expect of the target environments and what an existing deployed project can expect. My fuzzy recollection is that some pre-POSIX variants of As such, I'm strongly inclined to leave working code alone. I took the rename because it clearly was confusing, since I'd made an erroneous statement about the name, so fixing the confusion was good. But for the rest ... we'll have to see if someone else wants to take on responsibility for merging it. |
|
You're right. FWIW, here are two links for anyone wanting to consider this headache: As it happens, I may have conincidentally written compliant code. That said, as your typical sleepy IT person, it's much more likely to have typos, so while I'm less concerned about portability, I'm not remotely confident I didn't mess up something in the refactor. |
This is an attempt to make the code easier to follow and reuse pieces
It isn't tested, and given it's a refactor, it wouldn't shock me if I messed up.
This is what I was thinking about in #53
Please don't merge w/o careful consideration (and please fix the commit message).