On Wed, 30 Jul 2008 20:59:02 -0400
Simon <[EMAIL PROTECTED]> wrote:
>
> > distcc is, IMO, a bit more elegant than (for instance) trying to
> > manually emerge binary packages for machine A on PC B. You can tell
> > it to share the work or just unload it to the most powerful
> > machine. There ma
You might want to take a look at Coda instead of NFS. It supports
"disconnected" read/write: http://en.wikipedia.org/wiki/Coda_(file_system)
I haven't used it though.
Hey thanks! This seems quite cool! I've read about it on their website also
and it would clearly fit all my "requirements" f
I would perhaps do some more investigation & start a new thread about
distcc problems.
Yup, I'll do this major update on friday and report here about any issues
strictly related to emerge and distcc. However, no news is good news! =)
Thanks
On 31 Jul 2008, at 15:12, Simon wrote:
Yes, your words about "dependency" and "flexibility" are valid,
but this is also the most straightforward way to sync multiple
machines at once. If you do need to emerge a package when the
laptop is away from home then just --sync and it builds a port
Simon schrieb:
Your email is very long, so I'm not sure if I've taken it all in, but
what I'd suggest is a shared /usr/portage directory (easily done by
NFS) and distcc.
This creates a dependency on the host that contains the portage tree.
It also remove some flexibility. For example, taking
Yes, your words about "dependency" and "flexibility" are valid, but this
is also the most straightforward way to sync multiple machines at once.
If you do need to emerge a package when the laptop is away from home
then just --sync and it builds a portage tree at the "missing
mountpoint" (if tha
Stroller wrote:
On 31 Jul 2008, at 01:59, Simon wrote:
...
Your email is very long, so I'm not sure if I've taken it all in, but
what I'd suggest is a shared /usr/portage directory (easily done by
NFS) and distcc.
This creates a dependency on the host that contains the portage tree.
It al
On 31 Jul 2008, at 01:59, Simon wrote:
...
Your email is very long, so I'm not sure if I've taken it all in,
but what I'd suggest is a shared /usr/portage directory (easily
done by NFS) and distcc.
This creates a dependency on the host that contains the portage
tree. It also remove some
Hi Stroller, my email was probably as complex as I was confused, but you helped
a lot...
Your email is very long, so I'm not sure if I've taken it all in, but
what I'd suggest is a shared /usr/portage directory (easily done by NFS)
and distcc.
This creates a dependency on the host that conta
On 30 Jul 2008, at 00:09, Simon wrote:
...
I have 3 computers and they are all setup the same with the
exception of the kernel that has different options for the youngest
of my pcs. I'm looking for a simple, easy and efficient way to
keep them all up2date.
I want to avoid 3 --sync t
I don't have time right now to answer all of your questions, but in
terms of having all machines have the same list of installed packages,
all you probably need is /var/lib/portage/world . This lists all of
the packages that you emerged. I.e. those packages not brought in via
dependencies. If you
On Tue, Jul 29, 2008 at 4:09 PM, Simon <[EMAIL PROTECTED]> wrote:
> Hi,
> Below I explain my story, I show some difficulties and near the end ask a
> few questions, but last paragraph is my main question, comments on the rest
> is greatly appreciated.
>
> I have 3 computers and they are all setup
Hi,
Below I explain my story, I show some difficulties and near the end ask a few
questions, but last paragraph is my main question, comments on the rest is
greatly appreciated.
I have 3 computers and they are all setup the same with the exception of the
kernel that has different options
13 matches
Mail list logo
