From: Jonas Fietz <info@jonasfietz.de>
To: gentoo-server@lists.gentoo.org
Subject: Re: baselayout was Re: [gentoo-server] Stable portage tree
Date: Thu, 17 Aug 2006 13:20:19 +0200 [thread overview]
Message-ID: <44E450F3.1060505@jonasfietz.de> (raw)
In-Reply-To: <44E386FD.9090807@hyperreal.org>
Hi
> are a pain. I had to reboot a system that hadn't been booted in
> about a year and the modules didn't load because of the changes to
> modules.autoload. I've had to clean up Apache conf files 'cause they
> moved. I've had to deal with moving to the new "modular" xorg (and
> try to hunt down all the X tools I used to have). Not to mention
> the baselayout changes...
Well, Xorg was an upstream decision, the config-files for apache where
simply wrong before, so that had to be fixed, and about the changes in
modules.autoload, i am not so sure.
But to the people needing a stable portage tree: It is really a totally
different ideology which is somewhat diametral to what gentoo does.
Gentoo does _not_ have real releases, which some people, me included,
think is a good thing. Also, i think if the security-fixes are just
backported, I personally believe that unless there are many people
helping with the effort there will be more bugs introduced by this, as
most of the time the codes might not know the code base as well.
Also, you are complaining about the long list of updates when doing a -u
somewhat. Those are _real_ dependencies, even if they were just imagined
by some hallucinating gentoo dev ;). So normally there would not be a
way around installing them.
But on an infrastructure as big as some are talking about here, there
usually are few types of servers, so that it can be tested anyway. And
maybe, those types of companies should be more willing to spend a few
bucks to the gentoo project, maybe about the new "adopt a gentoo-dev"-page.
Ok, ranted enough ;)
Jonas Fietz
DISCLAIMER: I AM NOT A GENTOO DEV
--
gentoo-server@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-17 11:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 7:06 [gentoo-server] Stable portage tree Jan Meier
2006-08-16 9:01 ` Marten Persson
2006-08-16 9:19 ` Jan Meier
2006-08-16 9:36 ` Craig Webster
2006-08-16 9:50 ` Jan Meier
2006-08-16 10:00 ` Ian P. Christian
2006-08-16 10:19 ` Paul Kölle
2006-08-16 10:18 ` Ian P. Christian
2006-08-16 11:10 ` Paul Kölle
2006-08-16 11:26 ` Jan Meier
2006-08-16 13:12 ` Paul Kölle
2006-08-16 13:29 ` Jan Meier
2006-08-16 14:11 ` Paul Kölle
2006-08-16 14:40 ` Jan Meier
2006-08-18 21:25 ` Marius Mauch
2006-08-23 5:30 ` Sune Kloppenborg Jeppesen
2006-08-23 7:30 ` Jan Meier
2006-08-16 11:29 ` Alex Efros
2006-08-16 14:16 ` Jesse, Rich
2006-08-16 15:46 ` Alex Efros
2006-08-16 16:07 ` Ian P. Christian
2006-08-16 16:45 ` Alex Efros
[not found] ` <44E33DCA.4010407@hiramoto.org>
2006-08-16 16:04 ` Alex Efros
2006-08-23 5:32 ` Sune Kloppenborg Jeppesen
2006-08-23 5:34 ` Sune Kloppenborg Jeppesen
2006-08-16 19:21 ` baselayout was " Robert Welz
2006-08-16 20:58 ` Mark Rudholm
2006-08-17 11:20 ` Jonas Fietz [this message]
[not found] ` <Pine.LNX.4.64.0608161558030.606@matthew.jpcalvin.com>
2006-08-16 21:03 ` Dice R. Random
2006-08-16 21:11 ` Jesse, Rich
2006-08-17 12:45 ` Brian Kroth
2006-08-17 13:49 ` Jesse, Rich
2006-08-16 22:39 ` Robert Welz
2006-08-16 23:07 ` rdmurray
2006-08-17 9:15 ` Kerin Millar
2006-08-16 22:52 ` kashani
2006-08-16 22:59 ` Christian Spoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E450F3.1060505@jonasfietz.de \
--to=info@jonasfietz.de \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox