Release Highlights vanilla-sources-2.6.28.9 gcc-4.3.3 glibc-2.9_20081201-r2 openrc-0.4.3-r1 baselayout-2.0.0-r2 git-1.6.2.3 perl-5.10.0 bash-4.0_p17 app-sh/dash is now included in the tarball, in the next major release I hope to make it /bin/sh please test and report any bugs with doing this. apache2 and mysql are known to have issues. openrc works fine, the average desktop system should work. Known Issues emerge --sync will not clone the tree if it does not exist in portage 2.

I’d like to see multiple people merging the tree, with best case scenario being that it happens more than once a day. worst case status quo. I’m willing to write the scripts and teach anyone how to do it. I just ask that you can read an ebuild (to some degree) and have good judgement, or at least not too embarrassed to ask. Most ebuild merges are IUSE, KEYWORDS, and cvs line.

I haven’t forgotten about it. I seem to lack all motivation on Spring Break. Nothing to procrastinate on. Now that school has started I’m working in full swing, I’ve been learning metro the past few days. I should have the tarballs ready by the end of the week. I’m not sure on mirrors right now. Have at least one volunteer mirror, and I will be torrent-ing them. I’ve been seriously procrastinating on finding out how to get on the Uni mirror ring.

I think the idea of a meta distro on top of a stable base is the way to go, let people choose just what they want on bleeding edge. I like my kernel, gcc, and perl solid, sometimes I want firefox’s beta’s but that doesn’t mean I want the rest of the system like that. At some point gentoo’s ~arch became more stable that stable, this needs to end. Even if it means making stable a bit more unstable.

Last night I decided I’d be rolling out the first release of Regen2 in the first week of April.So as I’m sure everyone knows version are arbitrary they mean nothing… well ours are going to mean something. The first 2 numbers are the year, so 20(0.9).1.0. the Third number is the quarter, we are going to be mass stabilizing system once per quarter. I’m not sure that this will include new profiles.

This guide assumes that you’ve managed to install and start the postgres server. I’m ignoring these because they are well documented in several places, probably including your distribution, however, what to do next isn’t. First you need to connect to the Postgres database with psql as postgres, on gentoo* distributions you must be in the Postgres group to do this. In the event this doesn’t work you may have to su to the postgres unix user account somehow and run psql from there.

So 2 days ago, when I went to sync to gentoo I didn’t get any updates. I’m not really sure why as the process seemed to go alright. It could have something to do with the next bit.My System appeared to have been compromised. Syslog-ng was disabled and all logs post dec 30 2008 were removed. So i’ve spent the better part of yesterday/today reinstalling my system. Tree should be synced and merged tonight.

I’m going to be pushing out an new feature to portage today, since testing has gone well.SYNC_METHOD is a new portage variable, I’ve also gone to the trouble of defining it in make.globals. The default for Regen2. is git, however, rsync and cvs have also been defined although not tested.the main benefit of SYNC_METHOD is to use one way of detecting the program you should use to detect the tree. previous variations were problematic, as rsync does not have a directory like .

So after a little post about Regen2 on the Gentoo-dev mailing list. I’ve been offered mentoring to become an official gentoo dev. I’m conflicted, my main reason for saying yes would be to learn stuff that I can’t learn on my own. But I’m not sure I really want to be a gentoo-dev this means doing these other time consuming things, and I wouldn’t be able to do nearly enough from the inside.

So openrc was updated recently, and I noticed it, I decided it was time to find out why drobbins had created his own version. so I viewed them, ultimately I decided that drobbins had made too many changes but the gentoo ebuild had its own issues. So I modified the Gentoo ebuild to use EAPI 2, removed all of the live ebuild code that shouldn’t be in it, updated the branding, and we’re ready to rock.