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