Re: Files in DESTDIR but missing from flist

>> =======  3 extra files in DESTDIR  =========
>> Files in DESTDIR but missing from flist.
>> File is obsolete or flist is out of date ?
>> ------------------------------------------
>> ./usr/share/man/man3/DES_random_key.3.gz
>> ./usr/share/man/man3/HMAC.3.gz
>> ./usr/share/man/man3/MD5.3.gz
>> =========  end of 3 extra files  ===========
> 
> [To hoist more context out of subsequent mails: this is on macos, but
> the destdir is on a case-sensitive filesystem.]
> 
> Do you actually have those files?  They are long since obsolete, so I
> would like to understand how this was triggered on a system that
> doesn't have them to begin with.  I did touch this area of postinstall
> quite a while back, b/c exact-case checks were horrible for slower
> diskless systems, so I restricted it to just "Darwin".  From a quick
> glance to refresh my memory, that change should not have affected your
> case and I don't immediately see how the above could have been
> misdetected, so I'd like to get a better understanding of what's going
> on.
> 
> Independent of all of the above - your proposed change seems
> fundamentally right.  (Moreover, I think all obsolete man pages should
> have probably been marked with the ".man" keyword to do the right
> thing for the old systems that were built with compressed manpages.)
> 
> -uwe

I don't think it's related to file-system case-sensitivity.

My analysis:

- share/mk/bsd.own.mk defines HAVE_OPENSSL=35 (if not set otherwise).
- In that case, EXTERNAL_OPENSSL_SUBDIR=apache2/openssl gets defined.
- Whem apache2/openssl is built, man pages come from crypto/external/apache2/openssl/lib/libcrypto/man.inc, and
  in that file I found DES_random_key.3.

I guess, for OpenSSL 3.1, crypto/external/bsd/openssl should be built, and there is des_random_key.3 in crypto/external/bsd/openssl/lib/libdes/Makefile.

Which HAVE_OPENSSL setting do you use to build -current?

Adam