From: John Nilsson <john@milsson.nu>
To: Douglas Russell <puggy@bobspants.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage through SSH
Date: Sun, 31 Aug 2003 17:15:02 +0200 [thread overview]
Message-ID: <E4911160-DBC5-11D7-AC73-000393A27E82@milsson.nu> (raw)
In-Reply-To: <200308311601.23468.puggy@bobspants.com>
For me the problem is that the machines cant even run emerge sync, much
less search for deps and that kind of calculations. I want EVERYTHING
portage to be executed on one host (or with distcc a selected few) but
still be able to manage the software on the other hosts. Best would be
if I could uninstall portage from the other hosts completely.
-John
söndagen den 31 augusti 2003 kl 17.01 skrev Douglas Russell:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sunday 31 August 2003 3:35 pm, Marc Giger wrote:
>> On Sun, 31 Aug 2003 15:07:38 +0200
>>
>> John Nilsson <john@milsson.nu> wrote:
>>> Could one implement all packagemanagement emerge does through ssh
>>> (scp)?
>>>
>>> I would like to be able to use this command:
>>>
>>> emerge -u world server.mydomain.com
>>>
>>> where world, make.conf and other settings would be read from the
>>> server however the portage tree would be local so only one computer
>>> needs emerge sync, and packages would be crosscompiled for the server
>>> and then copied through ssh to the server.
>>>
>>> "emerge -u sendmail *.mydomain.com" =)
>>>
>>> This way I could spare my poor 486 from compiling duties.
>>
>> What's with distcc?
>>
>> DISTCC_HOSTS="compiling_hosts" emerge -u sendmail ??
>>
>> Just leave localhost away from DISTCC_HOSTS.
>> So it will only do preprocessing and such things on your 486. The
>> object
>> generation will do the "compiler_host...
>>
>> greets
>>
>> Marc
>>
>> --
>> gentoo-dev@gentoo.org mailing list
>
> distcc works well, but on my cyrix 166 the linking takes absolutely
> ages. It
> is much faster to just crosscompile for it on such a slow machine with
> the -K
> method mentioned in another email.
>
> Puggy
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
>
> iD8DBQE/Ug3CXYnvgFdTojMRAjoqAJ42yIx8R2QxYW1OSVDmcr33aNjP+QCfcncq
> kPL4ZUIkvmhjTsPs0SR1FfM=
> =tHGt
> -----END PGP SIGNATURE-----
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-31 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 13:07 [gentoo-dev] Portage through SSH John Nilsson
2003-08-31 13:32 ` Marius Mauch
2003-08-31 14:17 ` Luke-Jr
2003-08-31 14:20 ` John Nilsson
2003-08-31 14:35 ` Marc Giger
2003-08-31 15:01 ` Douglas Russell
2003-08-31 15:15 ` John Nilsson [this message]
2003-08-31 16:52 ` Georgi Georgiev
2003-08-31 18:14 ` John Nilsson
2003-08-31 18:29 ` Douglas Russell
2003-08-31 23:31 ` Steven Elling
2003-09-01 5:53 ` oom
2003-09-01 5:57 ` Seemant Kulleen
2003-09-01 10:43 ` Stuart Herbert
2003-09-01 7:04 ` Steven Elling
2003-09-01 7:51 ` Brian Harring
2003-09-01 16:51 ` John Nilsson
2003-09-01 16:55 ` John Nilsson
2003-09-01 17:34 ` Steven Elling
2003-09-01 19:34 ` Luke-Jr
2003-09-02 0:02 ` Terje Kvernes
2003-09-02 4:58 ` John Nilsson
2003-09-02 9:30 ` Terje Kvernes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E4911160-DBC5-11D7-AC73-000393A27E82@milsson.nu \
--to=john@milsson.nu \
--cc=gentoo-dev@gentoo.org \
--cc=puggy@bobspants.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox