No, I haven’t completed the port yet, but now I have a VM where FreeBSD 6.0 is installed and I can actually start the work.
The first part was the installation process, and that was bad enough because of my hacked evdev driver on the keyboard (I can’t use the arrows, I have to use the Keypad instead). Now it’s time to see if I can get a working chroot so that I can have a reference 6.0 system while creating the new setup (useful especially to get the libraries if I broke some of them, too 😛
I’m wondering if solar has something in portage-utils to find orphan files, because that would really be useful in this situation.
Preparing a 6.0 stage is not so different from preparing a new stage from scratch, with the sole difference that this time the ebuilds should be all already working.
I need to build (by hand) bash and those few packages portage requires, then python and last portage. For this last step I’m basically waiting portage 2.1_pre5, that should come out hopefully today 🙂
A bit of strange thing not finding screen in ports nor in packages, and not even in base system’s sources. I really want portage! 🙂
Oh and on another note: binutils-2.16 works fine with freebsd-lib, so that is what we’re going to use until someone wants to take time to fix freebsd-lib to build with binutils-220.127.116.11, so that –as-needed at least try to work 🙂