ltconfig uses bsdi4 in its checks.

So I changed my LOWER_OPSYS (used by ltconfig) to be "bsdi4" when OPYSYS
is "BSDOS".

But that broke my security/openssl/PLIST.bsdos that I committed on Oct. 4.

Should I make ltconfig use "bsdos" (which is not normal for ltconfig)?

Or should I just use "bsdi" for the
security/openssl/PLIST.${LOWER_OPSYS:C/([.0-9]*)$//}  ??

I am asking because it may be confusing for some to see PLIST.bsdi when it
should be PLIST.BSDOS.

Maybe the real problem is that security/openssl/Makefile does it this way.
Why doesn't it use PLIST.${OPSYS} like is normal (like in mk/bsd.pkg.mk)?

Should security/openssl/Makefile be fixed instead?
- PLIST_SRC=              ${PKGDIR}/PLIST.${LOWER_OPSYS:C/([.0-9]*)$//}
+ PLIST_SRC=              ${PKGDIR}/PLIST.${OPSYS}
(and rename files)

   Jeremy C. Reed
   http://bsd.reedmedia.net/