Neil Bothwick digimed.co.uk> writes:
> You wouldn't be able to use -march like this with two different cpus,
> you'd have to set it to something compatible with both, say i686. That's
> why I said "provided your USE and CFLAGS are the same" in my original
> post.
Got it.
Thanks guys...
James
On Thu, 13 Oct 2005 19:20:10 + (UTC), James wrote:
> Yes, OK. I want to play with this manually for a few weeks, then I'll
> use buildpkg and PGKDIR. One last qustion. If the USE settings are
> identical and the CFLAGS are similar between an AMD and Intel, can I
> use the approach with one sys
On Thursday 13 October 2005 03:20 pm, James wrote:
> Yes, OK. I want to play with this manually for a few weeks, then I'll
> use buildpkg and PGKDIR. One last qustion. If the USE settings are
> identical and the CFLAGS are similar between an AMD and Intel, can I use
> the approach with one system b
Neil Bothwick digimed.co.uk> writes:
> > Well, OK. But if I want to try this method manually first, then I'd:
> > 1. scp the var/lib/portage/world to the second system.
> > 2. ensure the make.conf USE setting are identical (they are)
> > 3. "emerge -uavD world"
> > 4. No need for the PKGDIR is
On Thu, 13 Oct 2005 16:37:39 + (UTC), James wrote:
> > Is the first portable always updated first? If so, I'd add buildpkg to
> > FEATURES in /etc/make.conf and make PKGDIR a directory accessible to
> > both, possibly via NFS. Then, provided your USE and CFLAGS are the
> > same (running the sa
Neil Bothwick digimed.co.uk> writes:
> I'd go with Unison, it's ideal for this sort of thing.
OK
> > AS far as keeping the installed packages /ebuilds/ concurrent,
> > in some sort of semi-automated method, I'd settle for a script
> > I could run that would check the installed packages, on bot
6 matches
Mail list logo
