1 |
Mark Knecht posted on Tue, 25 Apr 2017 10:43:29 -0700 as excerpted: |
2 |
|
3 |
> 3) Respectfully, I'm not sure your answer encompasses the problems and |
4 |
> frustrations of having to maintain OTHER people's computers. I don't |
5 |
> hear you speak of that very often. The problem with KDE is on my wife's |
6 |
> computer. When it's building KDE it's unavailable to her. In the past 2 |
7 |
> weeks I've had two massive builds that each took about 24 hours. That |
8 |
> amounts to about 15% downtime on her machine, |
9 |
|
10 |
What I'm trying to say, tho, is that if you set it up right, you'll only |
11 |
be building once, for your machine, or at least /on/ your machine if it's |
12 |
a package you don't yourself use, and will then be using already built |
13 |
binpkgs on her machine. |
14 |
|
15 |
So effectively it's like using a binary distro on everything except your |
16 |
build machine, only the binary distro will be customized with your chosen |
17 |
gentoo profile, USE flags, etc. |
18 |
|
19 |
IOW, bigger picture, the gentoo as metadistro idea, with you effectively |
20 |
creating the customized binary distro out of it with the build on your |
21 |
machine, that you then install on your wife's machine, and however many |
22 |
more you have around that you maintain or help maintain. |
23 |
|
24 |
Now depending on how similar the machines and layouts are, you may still |
25 |
end up building a /few/ packages individually for each or at least some |
26 |
of the machines, but if you choose your battles (packages) well, it'll be |
27 |
perhaps 10% of them, and "big" packages like gcc, firefox or chromium, |
28 |
etc, will only be built once. Tho if you have say kde on some and xfce |
29 |
on others, you might be building one or the other of them for perhaps one |
30 |
machine only, and certainly, kde at least is big, but still, if you're |
31 |
building for say 10 machines and a few packages are only used on one or |
32 |
two, with another few that you have to rebuild custom for each one, you |
33 |
might be building in total say 120% or 150% or even 200% of what you'd |
34 |
build for a single machine, but that's still way better than the 1000% |
35 |
(100% * 10) that you'd be building if you did each one individually. |
36 |
|
37 |
And while not /exacty/ the same as you'd get with all individual builds |
38 |
(the 1000%), it'd still be way closer to fully customized individual |
39 |
builds then the generic target mass distribution build you'd get using a |
40 |
normal binary distro. |
41 |
|
42 |
Meanwhile, the per-machine update and admin time, for other than that |
43 |
first build machine, would be very nearly the same as you'd spend with a |
44 |
mass binary distro anyway, and actually possibly less than the time you'd |
45 |
spend if you were splitting distros and having to keep up with the |
46 |
different ways different distros did things. |
47 |
|
48 |
At that point the update and admin time on your wife's machine would |
49 |
probably be /less/ staying with gentoo, because you'd be doing binpkg |
50 |
installs with already-built packages done on your main machine, and being |
51 |
gentoo, you'd know it better and be more effective at admin, so you'd |
52 |
actually spend less time on the admin side than you would if it were the |
53 |
only machine you had running ubuntu (or fedora or whatever), and thus |
54 |
dealing with any changes to config for the first and only time on her |
55 |
machine. |
56 |
|
57 |
-- |
58 |
Duncan - List replies preferred. No HTML msgs. |
59 |
"Every nonfree program has a lord, a master -- |
60 |
and if you use the program, he is your master." Richard Stallman |