tl;dr - can we add more automated tests to auto-generated stages? On 2/8/11 1:22 PM, Fabian Groffen wrote: > Hmmm, odd. I experience amd64 (stable) as being pretty stable on my > servers. Last breakage which really got me upset was php, but > that's already some time ago.
Makes sense. Most of the breakages I had in mind when starting this thread were related to consolekit/policykit/login manager/de breakages, or some desktop software not compiling with an updated gcc. Those issues generally don't affect servers. By the way, to turn this thread into some action: what testing do we currently perform for auto-generated stages? It'd be cool to at least compile-test that the stage can "emerge -e world" itself, and emerge some common packages (with FEATURES="test" so that we run at least some of the produced code). > With Gentoo you should update on fairly regular intervals, and have > the time inbetween as short as possible, but 2 or 3 weeks appears to > be fine. I myself have a cronjob that syncs every night, and mails > me the output of emerge -Dupv world. When this list gets too large, > it's typically about time to do some updating. Sounds like a good idea. I think I'll start using it. > I have masked new major releases of PostgreSQL and MySQL for > instance, and of course Python 3. Yeah, this ease of masking is a great strength of Gentoo.
signature.asc
Description: OpenPGP digital signature
