You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2020/02/18 23:49:38 UTC

[GitHub] [nifi-minifi-cpp] szaszm commented on issue #739: MINIFICPP-1163 Implemented.

szaszm commented on issue #739: MINIFICPP-1163 Implemented.
URL: https://github.com/apache/nifi-minifi-cpp/pull/739#issuecomment-587962342
 
 
   Let's collect the arguments on both sides and decide which approach is better!
   
   for config option defaulting to merge modules:
   * more choice on the use side
   * we transparently benefit from later updates to vcredist
   * recommended by microsoft (more than DLLs in app directory)
   * one less instance of duplicate DLLs on the target system, less disk space needed
   
   for shipping DLLs without merge module option:
   * simpler codebase, we don't have to maintain two kinds of packaging
   * no need to reboot the machine after installation
   * easier to implement
   
   Any more points for/against each side, or new suggestions? Is there a clear industry practice in this question?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services