From: Benda Xu <heroxbd@gentoo.org>
To: Lucas Ramage <ramage.lucas94@gmail.com>
Cc: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Re: Portage sync on demand
Date: Tue, 12 Jun 2018 23:32:53 +0900 [thread overview]
Message-ID: <87lgbkdqi2.fsf@proton.d.airelinux.org> (raw)
In-Reply-To: <CAKkjsY-i0=Bjfr+t3NpxfeaTOAFxrgq9DgaKsQXMWsUjo+9MVA@mail.gmail.com> (Lucas Ramage's message of "Mon, 11 Jun 2018 11:54:56 -0400")
Hi Lucas,
Lucas Ramage <ramage.lucas94@gmail.com> writes:
>>> I've used nfs and sshfs for mounting a remote tree
>> I would go this way when in short of storage.
>
> Are there any performance issues with this approach besides network
> speed/bandwidth.
>
> And let's say I'm not on WiFi. These are mobile devices after all.
>
> I'm thinking of a proxy server setup that could calculate dependencies
> on the fly and only download those specific ebuilds.
>
> Also, I could see GLEP 9 as being useful for updating over cellular
> networks.
Go for it.
>> Our IRC channel #gentoo-prefix freenode had a lot of discussions on
>> relocating Gentoo Prefix. The conclusion is that portage has support
>> for it built in, but outdated and need some extra love.
>
> That would be excellent. Python's virtualenv utility is pretty neat.
> It would be awesome if one could install portage inside of virtualenv,
> or to be able to `pip install --user portage`.
>
> Not sure how that would work technically.
I don't think venv is the correct way to handle system complexity. And
I don't understand what can be achieved by installing portage inside.
virtualenv It is a dirtier hack than what we do with Prefix.
Benda
prev parent reply other threads:[~2018-06-12 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1402A38B-9547-49BA-8343-57D5A1B0C247@gmail.com>
2018-06-08 19:03 ` [gentoo-alt] Re: Portage sync on demand Benda Xu
2018-06-11 15:54 ` Lucas Ramage
2018-06-12 14:32 ` Benda Xu [this message]
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=87lgbkdqi2.fsf@proton.d.airelinux.org \
--to=heroxbd@gentoo.org \
--cc=gentoo-alt@lists.gentoo.org \
--cc=ramage.lucas94@gmail.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