You may have seen this in your new port report recently: 16 Jul 2006 http://www.FreshPorts.org/devel/p5-Class-Multimethods-Pure/ http://www.FreshPorts.org/devel/p5-Luka/ Exception handling and reporting framework What is missing is a description for devel/p5-Class-Multimethods-Pure. It should be there. And if you click on the link provided, you’ll see it. So why doesn’t the description appear in the report? It’s all […]
No more blank descriptions Read More »
I’m in Charlottetown today, and waiting for a meeting to finish (I’m not in that meeting), so I thought I’d take the time to post this about newsfeeds. FreshPorts now has more newsfeeds in more formats than you could ever possibly want or need. We now have 9 formats, all available from one central location.
Newsfeeds in more formats than you will ever need! Read More »
I’ve fixed the cache problem. Reading the last few posts here, you’d know there have been a few cache problems. I’m hesitant to say it’s now all fixed, but well, I hope so. The latest problem related to clearing cache entries. It was a permissions issue. The script which removes the cache entries runs as
Cache problem fixed Read More »
I’ve managed to fix the caching problem previously mentioned. I think I solved it the night I wrote about it, but I’m only writing about it now. The code has been in BETA since then and has just moved into production. The log output now looks more like this: Observer has noticed that processing has
Caching process fixed Read More »
I found out exactly why the cache was not being cleared. Incorrect code. < my $CachingFile = $FreshPorts::Config::CachingRoot . '/cache/' . $category_name . '.' . $port_name; --- > my $CachingFile = $FreshPorts::Config::CachingRoot . ‘/cache/ports/’ . $category_name . ‘/’ . $port_name . ‘.*.html’; The first line is the existing production code. It refers to the old
Cache removal problems Read More »
I know we have a caching problem. I suspect I know the cause. The symptoms of the problem are: a commit has been processed by the system. the commit can be viewed via the URL /commit.php?message_id=MESSAGEID the commit can be seen via index.php or date.php the commit cannot be view on the port page I
Florent Thoumie mentioned today that FreshPorts should not supply package installation instructions for Restricted ports. Why? This extract from /usr/ports/Mk/bsd.port.mk indicates why # RESTRICTED – Prevent the distribution of distfiles and packages to # the FTP sites or on CDROM (e.g. forbidden by license # considerations). If we are not allowed to distribution the package,
Yes, we have no packages Read More »
Lars Engels had an idea. Why not have a place where you can download a port skeleton? You know, the files that make up a port (Makefile, pkg-plist, distinfo, etc). As Lars put it: It came to my mind when I tried out the Frenzy live cd yesterday. It does not have the iwi-firmware port
Link to download a port skeleton Read More »
I ran some tests today. Without caching, I got 5.36 transactions per second (tps). If commit history is cached, I get 7.25 tps. What actually happens in a transaction isn’t relevent. What is important is that by caching I get 35% more transaction per second. That is, the system performance increase by 35%. That’s pretty
Caching versus non-caching Read More »
In addition to the port history caching which I mentioned previously, I recently implemented some changes which will make it easier to cache yet more data. Specifically, the port details (e.g short description, long description). I’ve been playing with benchmarks/siege to see how many transactions per second I can put through my development server. Then