Date: Fri, 8 Feb 2002 08:07:59 -0800 From: "Kutulu" <kutulu@kutulu.org> To: "John Angelmo" <john@veidit.net>, <ports@FreeBSD.org> Subject: Re: FreeBSD Port: apache13-modssl-1.3.23+2.8.6 Message-ID: <003701c1b0ba$c7a4da80$81663244@longhill1.md.home.com> References: <3C637CC5.63F56D27@veidit.net>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "John Angelmo" <john@veidit.net> To: <ports@FreeBSD.org> Sent: Thursday, February 07, 2002 11:22 PM Subject: FreeBSD Port: apache13-modssl-1.3.23+2.8.6 > I removed old apache13-modssl and then ran cvsup to get the new, OK no > problem there but for some strange reason it removed files it shouldent > have removed (like stuff in the data dir) now I lost weeks of work. :( There is code in one of the FreeBSD patches to the Makefile that explicitly does the equivalent of an: rm -rf /usr/local/www/data.default This bit me the first time I upgraded apache13-modssl, too. The solution is to not put your own stuff in the default data directory, but make a seperate directory tree for it and symlink /usr/local/www/data to your custom content directory. The data.default directory can then be safely removed upon upgrade. > Shouldn't there be some kind of warning here? or simply not to touch > stuff it hasn't installd? It probably shouldn't do it at all. I don't beleive the non-ssl apache13 port does this, for example. --K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003701c1b0ba$c7a4da80$81663244>