So, before being a developer I used to maintain my own overlay on my site with many changed ebuilds, with extra patches and stuff. That’s how I actually ended up being a developer 🙂
Now, it’s been a while that I wasn’t publishing it, while I was still having things in overlay, obviously. The reason was that I wasn’t really sure how to provide, and what to provide in it anyway. I used to use tarballs but they took quite a bit of time to prepare and I can’t spend extra time just to package an overlay that little or no people would use.
With today’s work with Brian and bzr, I thought that might be a good way to handle it; I already managed my local copy with subversion, so moving to another SCM was not going to be difficult, and with bzr push command it was quite simple to let it online.
So now, if you want, you can get my overlay at [omissis]. It’s not a 100% complete overlay as I had it locally, as many things are still only on my overlay, mainly things that are not complete to final users.
The ebuilds on my overlay are obviously unsupported 🙂 I tried anyway not to put things that may screw users around, I originally put my patches for xkbdata and evdev driver I wrote this summer as applied unconditionally and that would break users not having and using an lx700 keyboard, but then I decided to put an lx700 userflag on the two so that they won’t break anything (hopefully). So if you want my lx700 patches just put lx700 in useflag and re-emerge xf86-input-evdev and xkbdata and you’ll get them 😛
I just hope it can be of help to someone 🙂