Re: [gentoo-amd64] Updating An Unconnected Machine

[Lie Ryan]

On 04/30/10 13:27, Frank Peters wrote:
> On Thu, 29 Apr 2010 13:09:59 -0600
> Dmitri Pogosyan <pogosyan@×××××××××××××.ca> wrote:
>
>> you can copy portage and distro files from connected machine (i.e it
>> will just serve as your local mirror), but you need to run emerge -Du
>> world on the unconnected machine, since it has different CFLAGS
>>
>
> Yes, it is my intention to run "emerge -Du world" on the
> unconnected machine.
>
> I suppose my actual question is whether or not "emerge --sync"
> updates anything else other than the ebuilds and other associated
> files of the portage directory, and I suppose that it does not.
>
> So copying the updated portage tree (updated via "emerge --sync")
> and copying the distribution files (acquired via "emerge -Du world")
> from the connected to the unconnected machine will allow an update
> by running "emerge -Du world" on the unconnected machine.
>
> I thought that I may be missing some details somewhere and that's why
> I raised the question on this list

I don't think there's anything wrong with that. Gentoo (and by
extension, portage) is an OS with comparatively very little magic
compared to other distros. I'm sure that you are aware that with your
current scheme, you can only install on the unconnected machine,
programs that is also installed on the host machine (and perhaps ones
which you run 'ebuild fetch' manually).

And probably you should take care not to overwrite the unconnected
machine's "world file" if you plan to have different set of programs
installed on both machine.

Portage creates downloadable daily .tar.bz2-ed snapshots of /usr/portage
for use on newly installed machine (look at the "Installing Portage"
step in the familiar handbook). You might want to look at what they're
packaging there (or even use that archive, perhaps).