From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by sourceware.org (Postfix) with ESMTPS id B75DA395540B for ; Thu, 8 Apr 2021 19:54:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B75DA395540B Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=theworld.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=bzs@theworld.com Received: from pcls8.std.com (pcls8.std.com [192.74.137.148]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id 138Jrs0S019678; Thu, 8 Apr 2021 15:53:56 -0400 Received: from pcls8 (localhost [127.0.0.1]) by pcls8.std.com (8.14.5/8.14.5) with ESMTP id 138JrnoR016649; Thu, 8 Apr 2021 15:53:49 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <24687.24397.711760.749444@gargle.gargle.HOWL> Date: Thu, 8 Apr 2021 15:53:49 -0400 From: bzs@theworld.com To: Andy Romens Cc: "cygwin\@cygwin.com" Subject: Re: Questions on how to upgrade Apache In-Reply-To: References: X-Mailer: VM 8.2.0b under 24.3.1 (x86_64-suse-linux-gnu) X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_50, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, T_SPF_HELO_PERMERROR, T_SPF_PERMERROR autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2021 19:54:05 -0000 I upgrade apache from sources all the time tho not on cygwin, we use Linux for that, but the basic idea is the same. My advice, having looked over other advice here, and your responses: 1. You probably don't want to go to another web server like nginx just for what you describe. You would have to reconfigure your entire web server environment including hosts, server certificates, dependent software (e.g., do your sites use php?), etc. That can be much more work and subtlety than just upgrading an apache dot release. 2. Although building apache from source is not very difficult there are build configuration options and even dependent software (I dunno, fastcgi, whatever) you would need to navigate. If you could get the exact build configuration (./configure ...options) that cygwin uses that might make it a lot easier. That result might "just work" since you're only trying to upgrade a dot release. But there may be other issues such as dependent software and dynamically loaded modules. Fortunately the configuration files (*.conf) between dot releases should just work, they don't change much if at all for the releases you describe. Given their configuration options it might be worth a try if you have the time and testing environment. 3. But then the pottery shop rule would kick in, you break it, you own it. By which I mean where do you go forward from there? Future releases? You will probably have to build from source forever or find some way to backtrack back into the binary cygwin releases. For us building and configuring from sources is fine but TBH on a scale of 1-10 I am an 11 on these things (pardon my modesty :-)). 4. Probably the best advice is: a) examine why someone thinks you need to do this at all other than they just like to run the latest and greatest. If it's security flaws consider that errors in doing this from source or going to another server entirely could be much more security-error-prone lacking in-house expertise. b) If they have such exotic and exacting requirements that they can't tolerate being behind a few dot releases then they should be willing to pay an expert to help them meet those requirements (no I'm not available.) In all seriousness and apologies to the cygwin crew who I love and admire the very fact that you're running apache on cygwin makes me think your requirements can't be too pie-in-the-sky, I'll guess you're not running Amazon or Shopify etc. c) Seriously consider a pre-built native Windows apache release. That should pretty much drop-in and if that seems too difficult the other options like building from source or switching to another server will likely be much more difficult. d) Apply to law school. -- -Barry Shein Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD The World: Since 1989 | A Public Information Utility | *oo*