What’s in the pipeline, how it works, how it’s made…
For several weeks, FreshPorts had a vuxml processing problem. In this blog post, I will share what I found. Introduction Incoming events for FreshPorts are handled by a small Python script which checks for flags and incoming commits. This ensures that work is carried out serially because parallel work can have unintended consequences. After each […]
Details of the vuxml processing problem Read More »
The previous post on this blog was nearly 10 months ago. However, things have not stood still. There have been a few issues fixed and some are still in progress. The biggest thing underway is a major rework of the backend, the part that processes the incoming commits. There is nothing major; no huge code
Redesign of FreshPorts backend Read More »
Committing to a branch (e.g. 2016Q4) when the port in question has slave ports is getting tricky, especially if the port was added after the branch was created. Case in point, www/linux-c7-flashplugin11 was added to the tree on 19 Oct 2016. The 2016Q4 branch was created on 3 Oct, and therefore that port does not
Committing to a branch when there are slave ports Read More »
$ grep -c 142.217.121.133 /usr/websites/log/freshports.org-access.log.0 72446
Hey 142.217.121.133, what are you doing? Read More »
I was asked if this was a known bug. It’s not. I don’t think anyone knows about it. dvl: ping. FreshPorts truncates COMMENT. Known issue? https://www.freshports.org/devel/include-what-you-use/ Here’s what I found there: Tool for use with clang to analyze Here is what the Makefile contains: $ grep COMMENT Makefile COMMENT= Tool for use with clang to
It’s not me. It’s you. Read More »
As you know, I’ve been working on branches this long holiday weekend. Today, I managed to get the display of a port on a branch to correctly. Along the way, I discovered a downside to storing raw data in the database. Take for example this output: This is the output of make -V RUN_DEPENDS. You
A downside of storing the exact results of ‘make -V’ Read More »
In my two previous posts I talked about creating a new port and copying a port from head to a branch. The goal of this post is the creation of a new function: CreatePortOnBranch($category_name, $port_name, $CommitBranch) The failed start I started out with this stored procedure: Running it gave this message: # select CreatePort(‘sysutils’, ‘bacula-server’,
A single function for creating a new port Read More »
In my previous post, I wrote about the need to copy a port from head to a branch in some circumstances, specifically when a master-port is updated and the slave ports do not already exist in the FreshPorts database on that branch. This is a side-effect of FreshPorts only taking action for commits, and not
Copying a port from head to a branch Read More »
The tracking of branches has turned out to be more involved than I thought. Many functions are already branch-aware and return / do the right thing. Tonight, I tried my recent idea of using head to get the slave ports for a given master port on a branch. So far, that works. The hard part
Branches – add a new port automagically Read More »
I used to think branches were simple when it came to FreshPorts, but I was wrong. Consider slave ports for example. If we get a commit for databases/mariadb100-server, we have to update the slave ports, but only the slave ports on the branch, not the slave ports on head. That sounds easy enough, but keep
Branches are simple, but more complex than head Read More »