Theo de Raadt writes:
>> I think the easiest path here is to incorporate the new upstream into a >> port, unless someone is familiar with zlib and can cherrypick out the >> commit(s) that resolve the issue. (I didn't find zlib in ports already.) > > That is completely impossible. It must be in base. There are 3 copies > in base -- userland, kernel, and bootblocks. They must be kept in sync. Not saying to replace what's in base, but have a different version in ports available for ports. I was thinking along the lines of egcc or eopenssl in that the port co-exists with base and ports that need them need tweaking to use them. > > It gets updated when things matter. I wasn't aware a change had happened > which matters. The thread makes me unenthusiastic, because I cannot tell > what changed that matters. Updating it is not a trivial effort, because > every bootblock needs testing. I've done it twice... I figured and want to be clear I am *not* volunteering for that exercise! I don't see a change that matters for base. -dv
