On Mon, 10 Nov 2003, Jens Hoffrichter wrote: > On Mon, Nov 10, 2003 at 11:36:02AM +0200, Eldad Zack wrote: > > > > This installed 'openssl-0.9.7' and removed 'openssl-0.9.6' - > > > unfortunately lots of stuff on the system was compiled and linked > > > against 'openssl-0.9.6' and they promptly broke. IE. Serious outage on a > > > production system. > > > > Not just that. if wget depends on openssl-0.9.6 and now the library is > > gone, you can't even download wget sources to perform a recompile. > > > > I'd suggest a special precaution with production enviornments - always > > build binary packages. > > That way you can roll back very fast if things don't work out. > > You can use quickpkg to make one from the existing filesystem if you're > > about to upgrade important packages if you didn't build a binary package > > in the first place. > Could you describe this a bit more detailed, please? How to make binary > packages? Or at least tell where to look for documentation? :)
look at the emerge manpage. when you merge new builds you can emerge -b - that will make portage build a binary (tbz2) as well as emerge into the system. If you want to make a binary out of the filesystem you've got now - It's as simple as "quickpkg package-name" and there's a manpage as well for quickpkg (it's part of portage). Just keep in mind one thing about quickpkg - (from the manpage): "The downside is that the package will contain the files that exist on your filesystem even if they have modified since they were first installed." Eldad -- [EMAIL PROTECTED] mailing list
