Re: [gentoo-server] Building binary packages

[Ricardo Loureiro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've been using binary packages for over 6 months and while they do  
work great there are some things that do not work as they should.

The main problem is USE flags, they are completely ignored if the  
system has different USE flags than the binary package, so you should  
make sure the machine making the binary package as exactly the same  
USE flags for that package as the machine which will be installing  
it. An 'emerge -vp package' should be enough.

I haven's actually tested for the same behavior regarding CFLAGS,  
since all machines were identical, but you should double check it.

The main problem is how to calculate the library dependencies. I  
would suggest you do the test on a separate machine, set the same  
environment as the target (same make.conf and profile) and update  
mysql. You could set  'buildpkg' in FEATURES inside your make.conf so  
it will create the binary packages while installing them. Do a revdep- 
rebuild and save the list of packages it will recompile. After you  
have that list and the test machine is working as it should, grab the  
binary packages that are created in /usr/portage/packages/ (if you  
haven't changed the default path) and install them in the target system.

This probably isn't an easy task, the easy way would be create binary  
packages of the stuff you really need (mysql, php, perl,<insert stuff  
you know depends on mysql>) on the test machine with the target  
machine specs and have them ready when upgrading. don't forget to use  
'emerge -k' to use binary packages instead of compiling them or  
'emerge -K' to only use binary packages and abort when a binary  
package isn't found.

Just occurred me, an easy way to determine which packages depend on  
mysql and will most likely fail if not rebuild is to use  
'equery' (need to install gentoolkit) and do an 'equery depends -D  
mysql' for a list of all packages (including indirect dependencies)  
that depend on mysql, and also 'equery hasuse mysql' for a list of  
all packages that have the mysql USE flag. This last one is most  
likely redundant, since it should be included in the list returned by  
the equery depends command.

The migration doc (http://www.gentoo.org/doc/en/mysql-upgrading.xml)  
explains how you can create a backup of your system, which you really  
should take a look, if you haven't already.

Hope it helps,
Ricardo Loureiro

On Feb 21, 2006, at 3:47 PM, 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
> --
> gentoo-server@g.o mailing list
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFD+1XmJePPaWt8DsARAmIzAJ0UNTWyKTguNp83d58h4pyEdcMiAQCdF4Lh
xvSpsgaZ35oXfgM1lGlPCCE=
=fCZh
-----END PGP SIGNATURE-----
-- 
gentoo-server@g.o mailing list