Mmm … the 2X tarball includes the source code for a large number of components that we can provide through Portage, and their build script is very easy to read (if only that could be said about all upstream packages! 
)
If I get the ebuild to do the work instead of using their build script (which doesn’t work out of the box anyway, as it’s designed to work with a subversion checkout), it might not take that long to get something available for testing.
Mmm.
Be the first to leave a comment »
Booted the box on Friday evening, only to be greeted by the dreaded “Invalid partition table” error all the time. Ho hum. Time for a new disk. Damn thing was only two years old too, and it’s not a machine that’s ever been regularly used.
I’ve managed to get the box self-hosting again, but I’ve had other things to do this weekend, so it’ll be a few days before I’ve re-installed Gnome and KDE onto the box. Apologies to folks who are waiting for an amd64-compatible ebuild for FreeNX; it’ll be a few more days yet.
Although, tbh, you’re not missing much … I honestly can’t see me asking for FreeNX being marked stable on x86 until the orphaned processes bug is tracked down and resolved. And I’m seriously having second thoughts about whether I want to spend the time on that or not.
In the meantime, the folks at 2X have very kindly created the source tarball we need to get their GPL’d NX server and client into Portage. At 108M in size, it’s quite the download, and it’ll take me a few mornings to get it all compiled here on the laptop (I normally spend an hour every morning in my local Starbucks working on Gentoo stuff, before heading off to the office), but it’ll be worth the effort. Thank God for ccache, that’s all I can say!
Mmm … shame I can’t afford a new Mac Book Pro Core 2 Duo this side of the holiday season
Be the first to leave a comment »
