Re: [gentoo-dev] Portage through SSH

[Terje Kvernes]

(I generally don't reply to top-posted articles, but oh well)

John Nilsson <john@×××××××.nu> writes:

> rdist is probably great if you would like to have identical hosts.

  you don't need to have identical hosts with rdist.

> But if you are having diffrent kind of installations it could get
> messy.

  hm, could you define "different kind of installations"?  :-)
 
> I was thinking something along these lines.
>
>   %emerge sync && emerge world --target server1 --update
>
>    1. rsync to localhost
>
>    2. read localhost:/var/cache/edb/server1/world || \
>       read server1:/var/cache/edb/localhost/world
>
>    3. calculate which packages have to be updated
>
>    4. read localhost:/var/cache/edb/server1/make.conf || \
>       read server1:/etc/make.conf
>
>    5. download and compile localy
>
>    6. install to server1:/
>
>    7. modify server1:/var/cache/edb/localhost/world && \
>       modify localhost:/var/cache/edb/server1/world

  honestly?  no.  there are a lot of other things that should be fixed
  in Portage before this ever gets on a drawingboard, if it even
  should get there.  

  if you want this functionality, my best advise would be to build a
  buildroot on your build host using chroot, and remove stuff you
  don't want when you rdist it to the client.  otherwise you could use
  buildpkg and just install packages on the client.  even a stripped
  system should have 'tar'.  :-)

  this would also leave the whole task transparent to Portage, which
  is good[tm].  actually, this isn't too different from how I deal
  with my NAT-box.

-- 
Terje

--
gentoo-dev@g.o mailing list