1 |
Mark Knecht posted on Sat, 22 Apr 2017 11:38:59 -0700 as excerpted: |
2 |
|
3 |
> As for my wife's laptop which started this discussion I had an emerge 2 |
4 |
> weeks ago of about 200 packages, mostly KDE, which took almost 24 hours |
5 |
> to build on a 5-6 year old laptop.This time around I have about 175 |
6 |
> packages today. We'll see how long it takes as a data point but I've |
7 |
> decided to move her to Ubuntu. I think I need to be spending my time |
8 |
> more productively than building this much code this often. I already run |
9 |
> Ubuntu as a VM on my Gentoo machine due to apps not supported (or not |
10 |
> building correctly) by Gentoo in portage. Sad as it will be the first |
11 |
> non-Gentoo boot in my house in about 15 years. |
12 |
|
13 |
Is her laptop 64-bit or only 32-bit? Either way, how many other machines |
14 |
of similar bitness do you have around? (I'm presuming all x86 or amd64, |
15 |
no arm/mips/ppc/whatever.) |
16 |
|
17 |
Some time ago I had a 32-bit netbook and my 64-bit main machine. I |
18 |
update the main machine frequently, often a couple times or more a week, |
19 |
but found myself falling behind on the netbook (which I built in a 32-bit |
20 |
chroot on the main machine and secure-rsynced over), not updating it for |
21 |
a year or more at a time, sometimes, so it was a *BIG* job when I finally |
22 |
/did/ update. (FWIW, there was, very deliberately, nothing private on |
23 |
the netbook, and contrary to the name, it wasn't net-connected most of |
24 |
the time anyway, so I wasn't really worried about the security |
25 |
implications of not updating for that long.) |
26 |
|
27 |
My takeaway from that was to make everything the same arch, loosen up the |
28 |
c(xx)flags somewhat to build a bit more generically, adjust USE flags to |
29 |
be a bit more generic as well, and do binpkg builds which I can then |
30 |
emerge -k onto all machines. That way I'm building most things just |
31 |
once, altho I imagine I'd customize USE flags and/or c(xx)flags on a few |
32 |
packages. |
33 |
|
34 |
I haven't really gotten the other machines yet that I have in mind, but |
35 |
ultimately, I want, probably, a repurposed chromebook for portability, |
36 |
and a small, effectively embedded system with a bunch of gigabit ethernet |
37 |
ports and wifi, for a router. Thus the message I posted here a couple |
38 |
years ago, getting ideas. (I got a bunch for the router, not so much for |
39 |
the chromebook replacement or similar.) |
40 |
|
41 |
So obviously I've not set it up yet, but the idea is sound. If I have |
42 |
more than one machine, make sure they're all the same arch and build most |
43 |
things just once, to install on everything from the router to the |
44 |
netbooks to the main machines. After the first build, presumably on the |
45 |
main machine, everything else in common at least would be either binpkg |
46 |
updates, or perhaps rsync updates. |
47 |
|
48 |
Of course if her machine is 32-bit x86 and it's the only one you have, |
49 |
you're in the bind I was in and can't really share with anything else. |
50 |
But you can still setup a 32-bit chroot on your presumably faster main |
51 |
build machine and build there, so at least the builds shouldn't take as |
52 |
long... unless of course you let it get a year-plus behind, like I did, |
53 |
and have to figure out how to actually get all the updates thru once you |
54 |
/do/ update. |
55 |
|
56 |
But having been there, if it's about your only 32-bit only machine or is |
57 |
otherwise the odd one out, I wouldn't blame you at all for sticking |
58 |
whatever binary-based distro on it. Tho FWIW I'd probably make it arch, |
59 |
not ubuntu, but that's just me. If ubuntu's more her, or your, style, go |
60 |
with it! =:^) |
61 |
|
62 |
-- |
63 |
Duncan - List replies preferred. No HTML msgs. |
64 |
"Every nonfree program has a lord, a master -- |
65 |
and if you use the program, he is your master." Richard Stallman |