Re: [gentoo-server] Building binary packages

[Francesco Riosa]

Thomas Schreiner wrote:
> Hi,
>
> my problem upgrading to mysql-4.1 is the downtime that I am going to get
> while the new build completes.
>
> That's why I was planning to build a binary package for mysql-4.1 on a
> second host in order to install it on my production server, but I could
> not find a list of common pitfalls to consider while building packages
> for a different host. These are the things that I can think of so far:
>
> - appropriate make.conf, CFLAGS etc.
> - right USE flags (or make.profile in general)
> - same version of libraries / dependencies to prevent dynamic linking of
>   libraries that don't exist on target host (that's going to be a hard one)
>
> Is there a HowTo that lists all things to consider, or is it a
> generally discouraged thing to build packages for another host if the hosts
> are not 100% the same?
>
> Thanks a lot
>
> Thomas
>

There are different ways to decrease the downtime, the one that follow
nearly the route you chose (and is less dangerous) is to:

# emerge --buildpkgonly =mysql-[version]
# emerge -pv --usepkgonly =mysql-[version]
# /etc/init.d/mysql stop
# emerge --usepkgonly =mysql-[version]
# /etc/init.d/mysql start

if you're upgrading from mysql-4.0 then it's not so easy and google will
help.

beware that if you are switcing to slotted mysql many people had
problems due to different bugs, that should be mostly solved now but ...
there is a doc [1] to read before to do that kind of upgrade.

To achieve zero downtime you need something like a "replication" setup
and such, this could be a lengthly explanation and will covered only if
needed ;-)

[1] www.gentoo.org/doc/en/mysql-upgrade-slotted.xml

-- 
gentoo-server@g.o mailing list