From owner-freebsd-questions@FreeBSD.ORG Mon Sep 15 00:06:02 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DE1A16A4BF for ; Mon, 15 Sep 2003 00:06:02 -0700 (PDT) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [212.184.201.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B32B43FBD for ; Mon, 15 Sep 2003 00:06:00 -0700 (PDT) (envelope-from dirk.meyer@dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [212.184.201.182]) by uucp.dinoex.sub.de (8.12.9/8.12.9) with ESMTP id h8F651G4008538; Mon, 15 Sep 2003 08:05:01 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) Received: from gate.dinoex.sub.org (dinoex@localhost)h8F6509b008526; Mon, 15 Sep 2003 08:05:01 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) To: freebsd-questions@freebsd.org, culley@fastmail.fm (culley harrelson) Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Date: Mon, 15 Sep 2003 07:55:25 +0200 X-Mailer: Dinoex 1.79 References: X-Gateway: ZCONNECT gate.dinoex.sub.org [UNIX/Connect 0.94] X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-ZC-TELEFON: V+49-5606-6512Q F+49-5606-55023 X-Copyright: (C) Copyright 2001 by Dirk Meyer -- All rights reserved. X-ZC-POST: Im Grund 4;34317 Habichtswald;Germany X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20030915000000S+2@dinoex.sub.org Subject: Re: apache13 to apache13-modssl port migration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 07:06:02 -0000 I wrote: > > > > The transition is easy. > > > > 1) deinstall all your ports(modules) depended on apache13 > > 2) install apache13-modssl. > > 3) recompile all ports(modules) > > > > You can use apache13-modssl just as a replacment to apache13. > > But apache13-modssl uses extrand API, so you have to > > recompile all apache modules with "apache13-modssl" installed. > > > > all modules will build, install and run fine, maybe portupgrade > > will see wrong dependencys. > > > > some ports suports this very well using in /etc/make.conf > > APACHE_PORT= www/apache13-modssl > > > > still some ports use a "obsolete" setting like: > > APACHE_PORT= ${PORTSDIR}/www/apache13-modssl > > AP_PORT= www/apache13-modssl > > AP_PORT= apache13-modssl > > > > This might be improved after The 4.9 Release > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/32604 cully wrote: > Would you avoid portupgrade for this? > > I am a little shaky in the knees at this prospect. This is on a > production web server getting over 1 million page views per day. I use > mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports > installed like squirrelmail, mnogosearch, a bunch of pear libraries (not > even sure if they are dependent on apache13), phpMyAdmin and probably a > few other things I haven't even thought of. > > Once this is done do all these ports change to think they are dependent > on apache13-modssl rather than www/apache13? Yes, the PR#32604 will fix this. But even now, you don't have to worry, just be sure the modules are compiled with only www/apache13-modssl installed, if portupgrade dones not overwrite with with "www/apache13" in some coases you are perfectly fine, even if some ports register a wrong dependency. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [dirk.meyer@dinoex.sub.org],[dirk.meyer@guug.de],[dinoex@FreeBSD.org]