This is just a feature concept. May or may not ever happen. Live builds for portage usually run off the trunk/master branch of a scm tool. This is a great idea, but why couldn’t we take this a step further, usually people who use scm’s ‘tag’ there releases, so why couldn’t the same ‘live’ build have an option for using a tag instead of trunk. This would allow releases to roll out much faster too.

I’m sure you’re thinking I’m talking about me ;) nope first order of business, add more stuff which should be in gentoo. I’m pleased to announce that I’ve added py3k also know as Python 3.0 to Regen2. It will remain hardmasked as unmasking could create stability issues on a gentoo based system given it’s reliance on python.

So, I won’t be the Tree Maintainer for Funtoo anymore. In light of the new situation I’m forking Funtoo. I’m not going into details why I’m not the tree maintainer anymore on this blog, except to point out how Regen2 will differ.I’ll be continuing to maintain a tree with all the overlays I had added and more to come. you can get a copy of my version of portage at git://github.

I’ve decided I’m going to start posting a sort of weekly newsletter (I’m not committing to weekly though) merely to document anything I feel important that happened, or is about to, but isn’t quite important enough for it’s own post.RA(ra– on #funtoo) or r_a@lavabit.comsubmitted quite a few patches this week including 1 that fixes many of my major borkage on non-latin1 changelog breaks. He’s become a regular contributor and I’d like to thank him.

Soon, Dan Robbins will be merging my perl-experimental branch which contains the perl-experimental overlay. This overlay contains a handful of packages, the most important of which is perl-5.10.0 which has been out for about a year now and Gentoo still hasn’t put in portage. One nuisance of the perl-experimental overlay is they don’t use changelogs which means if you want to know what’s going on with a package from this you’ll have to check out git log as well as the changelog.

Sunrisea Gentoooverlayis being added to Funtoo. So if you’ve got layman tracking sunrise and you’re using funtoo you’ll be able to delete sunrise from your overlays as I’ll be merging sunrise’s reviewed ebuilds daily.The hardest part of the whole process was merging package.mask, use.local.desc and categories. Since this is new be on the lookout for bugs or problems.Want to add an overlay to funtoo yourself? First, it’ll have to be a git or svn overlay.

HereI explain why emerge –sync should return to it’s original sync form.I think emerge sync should have the ability to have a target. Currently emerge –sync has a target of the SYNC variable in make.conf or the default hardcoded. However, git support is being added to portage. git is a very powerful tool, and the Funtooproject uses it to manage it’s full portage tree. git doesn’t work like rsync, it’s not so straight forward as rsync uri, which is effectively what emerge sync is doing.

Ok so I have yet another idea for portage and other portage like package managers. actually this is probably more aimed at EAPI. Different types of USE flags. The 2 I’m thinking of off the top of my head could be described as volatile and non-volatile. Basically a use flag marked volatile means a package needs to be recompiled if it gets changed one marked non-volatile most likely just pulls in another dependency or copies files such as documentation.

That’s right I’m putting my money where my mouth is. It’s small but the first 2 packages when into the regen2 treethis morning. They are MySQL 5.1.30 which was added because the gentoo maintainer refused to add it do to instability. I agree that it is unstable, but we have ~M Hard Masked packages for that reason. It has been added as ~M. The other app added is qsynergy, the ebuild was already on portage and I know it to be good so I added it to the tree, I’ll probably stabilize it in a few weeks.

I like security… which means I should be able to run portage as portage (user) and have the umask be 077, or perhaps 027. Unfortunately the last time I checked portage could handle these restrictive permissions (I forget if it was these exactly) except for one set… java. In a perfect ebuild world all ebuilds would be able to be installed under a very restrictive umask.Should regen2 ever come to fruition this should be fixed.