1 |
Technomancer wrote: |
2 |
|
3 |
> I choosed Gentoo because using other distros I could not build the |
4 |
> system the way I wanted without headache. |
5 |
> |
6 |
> On most cases there was the necessity of package compilation, ignoring |
7 |
> the package management systems of most distros. This sounds like chaos |
8 |
> to me. |
9 |
> |
10 |
> Using Portage I coul add and remove features of programs like Postfix |
11 |
> without making some ugly workaround. |
12 |
|
13 |
I migrated to Gentoo for the exact same reasons, I needed to be able to |
14 |
customize deployments. In my opinion this (portage) is the most |
15 |
significant strength of Gentoo. |
16 |
|
17 |
It is not, however, without its challenges. In my experience it is pure |
18 |
insanity to attempt to maintain upgrades directly on servers. You will |
19 |
definitely want to maintain a deployment test environment to work through |
20 |
any problems after syncing your portage tree before attempting to apply |
21 |
upgrades to production servers. I wrote a utility to do this - |
22 |
http://badpenguins.com/source/gentoo-buildhoster/ if you are interested in |
23 |
trying it out. |
24 |
|
25 |
As far as managing config files and such, I have rarely had problems |
26 |
managing them via dispatch-conf. There are situations that will bite you |
27 |
in the ass if you are not careful though, debacles such as forced upgrades |
28 |
to a new apache config file layout, radically different installations of |
29 |
php between upgrades, disappearing kernel source ebuilds, and so on. Hence |
30 |
my suggestion to do any upgrades in a test environment before pushing them |
31 |
out to the servers ;) |
32 |
|
33 |
-- |
34 |
gentoo-server@g.o mailing list |