Development

I’ve created myself an IPv6 tunnel. FreshPorts is now available via IPv6. Point your browser at http://pg8.freshports.org/. If you can’t get there, you’re probably not on IPv6. You should see a snapshot of FreshPorts taken on Fri, 23 Dec 2005. Comments here please!

When I started writing FreshPorts (The Place For Ports) back in the late 1990’s, I was under the impression that a port had just one version. The current version. There is only one ports tree. There isn’t one ports tree for FreeBSD 4 and another for FreeBSD 5, and yet another for FreeBSD 6. There’s

krion pointed out today that when a port moves, your watch list is not updated. In this case, the port in question is dns/libidn. It’s listed as version 0.6.0 at the above URL, but in his watch list, he sees version 0.5.20. I saw the problem immediately. On his watch list, the port is listed

If you have installed portupgrade, then you have portcvsweb. What is portcvsweb? Here’s a bit from the man page: portcvsweb — a tool to instantly browse a history via CVSweb That’s nice! Then, this morning, I thought about integrating this with FreshPorts. So I can up with this little patch: [dan@bast:~/bin] $ diff -ru /usr/local/sbin/portcvsweb

The New Ports page is not sorting by date. I guess you haven’t noticed. Well, it is sorting by date, but alphabetically, not chronologically. Have a look at the above URL, then compare it with what I have done in my develoment site. You’ll see that the first sorts alphabetically, the second actually gets the

I heard someone mention that the categories page loaded slowly. That’s to be expected. It’s figuring out the last commit in each category. Calculating the number of ports in each category. And it’s doing this for both physical categories and virtual categories. There are about 16000 rows in the ports table, and about 94 categories.

Now that I think about this… I’m sure there is something in the relational integrity to ensure that if a parent is marked as deleted, the children are mark deleted as well. Perhaps I need something to mark parents as active if a child is reactivated. I’ll check. In the meantime…. I couldn’t sleep, so

FreshPorts runs on an i386 machine under FreeBSD 4.11. That means all the information it contains, relates to that Branch (4.11) and that architecture (i386). Moves are underway to make FreshPorts branch and architecture independent. One of the main bits I needed for this was a way to know the the latest value for __FREEBSD__

Sam Lawrance found a bug. If a port is deleted, then a file added back in, and then it’s removed, FreshPorts doesn’t know that the port is deleted. He found this with x11/ruby-gnome. You can see that it is marked as an expired port. On 05 Nov 2005 08:07:45, kris removed it from the tree.