Re: Upgrading Production www Servers, MySQL Servers, etc, etc

• Previous message: marlon corleone: "ports-supfile config"
• In reply to: Max Clark: "RE: Upgrading Production www Servers, MySQL Servers, etc, etc"
• Next in thread: Alexandr Kovalenko: "Re: Upgrading Production www Servers, MySQL Servers, etc, etc"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

To: "Lewis Watson" <lists@visionsix.com>
Date: Fri, 25 Jul 2003 12:31:22 -0400

----- Original Message -----
From: "Max Clark" <max.clark@media.net>
To: "Lewis Watson" <lists@visionsix.com>; <freebsd-isp@FreeBSD.ORG>
Sent: Thursday, July 24, 2003 8:12 PM
Subject: RE: Upgrading Production www Servers, MySQL Servers, etc, etc


> Hi,
>
> Portupgrade compares the version of the port installed vs. the version of
> the port available in the ports tree. So for it to be useful you must be
> running cvsup and updating your ports collection. After you run cvsup you
> can modify the makefile and then run portupgrade which would give you the
> desired effect you are speaking about.
>
> /Max

There is an issue here in that subsequent cvsup will overwrite your Makefile mods. If you want to make your changes perment, there are a couple of tricks.

Various compile flags can be set in /etc/make.conf. Lots of flags are defined in /usr/ports/Mk/* (especially /usr/ports/Mk/bsd.port.mk). However, be wary of flags used in common with other ports. make.conf is read pretty early in the process (e.g. before ${PORTNAME} is defined) so defining something like ${CONFIG_ARGS} in make.conf is a bad idea.

/usr/local/etc/pkgtools.conf allows per port customization of a number of settings as long as you always use portupgrade. It's a ruby file (which I don't grok); but the syntax is pretty straight forward; and there are lots of examples.

If you don't want to be dependant on portupgrade, bsd.port.mk also reads in /usr/src/../Makefile.inc late in the compile process (e.g. after ${PORTNAME} is defined). I have used this to hook a separate /etc/make.port.conf. I have no real idea why this file is included; so I can't swear that it will always work going forward. However, it has been helpful for the last couple of years.

> -----Original Message-----
> From: owner-freebsd-isp@freebsd.org
> [mailto:owner-freebsd-isp@freebsd.org]On Behalf Of Lewis Watson
> Sent: Thursday, July 24, 2003 5:01 PM
> To: freebsd-isp@FreeBSD.ORG
> Subject: Upgrading Production www Servers, MySQL Servers, etc, etc
>
>
> Hi List,
> I asked a couple of questions a few months ago about upgrading ports on
> production machines and portupgrade seemed to be a recommended tool for
> this, even on production servers. So now I have questions about
> portupgrade :-)
>
> I want to use port upgrade to upgrade ports but what about ports where I
> have modified the Makefile? Will I get the opportunity to modify the
> Makefile after it downloads the newest port; but before it installs? I
> have dug around for tutorials/ how-to's for portupgrade but I have not
> been so lucky as to find answers regarding this.
> Thanks for help!!
> Lewis
>
>
> _______________________________________________
> freebsd-isp@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
>
> _______________________________________________
> freebsd-isp@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
>

_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"

• Previous message: marlon corleone: "ports-supfile config"
• In reply to: Max Clark: "RE: Upgrading Production www Servers, MySQL Servers, etc, etc"
• Next in thread: Alexandr Kovalenko: "Re: Upgrading Production www Servers, MySQL Servers, etc, etc"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]