1 |
You can separate the package directory and distfiles directory from the |
2 |
ebuild tree. |
3 |
|
4 |
PORTDIR="/usr/portage" |
5 |
DISTDIR="/usr/portage-distfiles" |
6 |
PKGDIR="/usr/portage-packages" |
7 |
|
8 |
|
9 |
That lets you keep the ebuilds local to your laptop. |
10 |
|
11 |
|
12 |
On Wed, Feb 26, 2020 at 9:08 PM William Kenworthy <billk@×××××××××.au> |
13 |
wrote: |
14 |
|
15 |
> PORTDIR="/mnt/mfs/portage" |
16 |
> |
17 |
> /mnt/mfs is a moosefs fuse mount |
18 |
> |
19 |
> shared full tree including distfiles, and separate package files for |
20 |
> different hardware groups |
21 |
> |
22 |
> |
23 |
> BillK |
24 |
> |
25 |
> |
26 |
> |
27 |
> On 27/2/20 9:56 am, Michael Jones wrote: |
28 |
> |
29 |
> When you say you have a remote portage. What do you mean? |
30 |
> |
31 |
> The actual portage tree, with all the ebuilds? Or something else? |
32 |
> |
33 |
> On Wed, Feb 26, 2020, 18:08 William Kenworthy <billk@×××××××××.au> wrote: |
34 |
> |
35 |
>> Hi, |
36 |
>> |
37 |
>> due to space considerations on my laptop I have moved portage onto a |
38 |
>> network share (moosfs, mfsmounted) - slower but works fine. However, |
39 |
>> being a laptop trying to update/install when out and about is both very |
40 |
>> slow and network intensive through a vpn - again, it works but is even |
41 |
>> slower to the point of not always being practical |
42 |
>> |
43 |
>> Is there a way to localise/speedup portage scanning parts of the |
44 |
>> update/install process? |
45 |
>> |
46 |
>> 1. put it on a squashfs share to save space (the laptop is running btrfs |
47 |
>> with compression so I don't think that will get me much) |
48 |
>> |
49 |
>> 2. put portage on an sd card and mount it when necessary |
50 |
>> |
51 |
>> The laptop is a Surface Pro4 so expanding the storage is not practical - |
52 |
>> though I could shrink the windows partition a little more. |
53 |
>> |
54 |
>> BillK |
55 |
>> |
56 |
>> |
57 |
>> |
58 |
>> |
59 |
>> |