1 |
On Sat, Aug 13, 2016 at 10:08 AM, hw <hw@×××××.de> wrote: |
2 |
> |
3 |
> I infrequently update Gentoo because I´m *always* running into problems |
4 |
> like this. 'Infrequently' means about every 3 months at home, and not |
5 |
> since, IIRC, 2015-02 here at work. The last update at home got stalled |
6 |
> because perl cannot be updated, and I haven´t had the time to look into |
7 |
> that to finish it. |
8 |
|
9 |
You're probably always running into problems like this because you |
10 |
infrequently update Gentoo. |
11 |
|
12 |
If you ran it every day you'd probably only run into issues every |
13 |
couple of months, and when you did you'd have it immediately narrowed |
14 |
down to a few packages since that is all that has changed. |
15 |
|
16 |
> |
17 |
> If you say that you need to update more frequently than every 3 months |
18 |
> for not to have problems with the update process itself, I can only |
19 |
> conclude that Gentoo is entirely unsuited for servers --- and for home |
20 |
> use as well other than for test machines perhaps. |
21 |
> |
22 |
|
23 |
If you're looking for a distro designed to just work with no hands-on, |
24 |
then you should probably look elsewhere. |
25 |
|
26 |
Put it another way, why are you using Gentoo instead of Debian or |
27 |
CentOS in the first place? |
28 |
|
29 |
Gentoo is useful when you want to mess with the configuration of the |
30 |
distro itself, not when you just want to throw a few files in |
31 |
/var/www/htdocs and be done with it. |
32 |
|
33 |
Gentoo can be made to work rather well on servers, but you have to |
34 |
know what you're doing. You can't just run emerge -u world on a |
35 |
production server that hasn't been touched in a year and expect to |
36 |
work. However, you certainly could set up your own local repository, |
37 |
pull in updates as needed (certainly including frequent security |
38 |
updates), build binary packages and deploy to your test environment, |
39 |
make sure everything is good, and then deploy those binary packages to |
40 |
your production servers. You can accomplish a lot of things that way |
41 |
that you couldn't accomplish with CentOS or Debian. |
42 |
|
43 |
However, if all you want is the same binaries Debian already gives |
44 |
you, then just run Debian. It isn't like apache runs better just |
45 |
because you compiled it yourself. Gentoo is about tweaking things. |
46 |
And if you're going to tweak things in an enterprise environment then |
47 |
you need to be doing QA. |
48 |
|
49 |
If you really want to be deploying updates into production without any |
50 |
testing then you ought to stick with the likes of CentOS/RHEL. That's |
51 |
basically their entire value-add. Debian stable would be another |
52 |
option. |
53 |
|
54 |
-- |
55 |
Rich |