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 »
This afternoon, Bert JW Regeer wished that FreshPorts “would show information from the quarterly branches too…”. I knew I had done some work on this and that there was a way to display branch information. I check the source code and found the ?branch= parameter, but there was nothing in the database for this branch.
Quarterly branches are available Read More »
FreshPorts is not magic. It grabs the stuff it needs by running make -V with a number of parameters. New fields are added from time to time, usually at the prompting of a user. Recently, the following fields were added to the dev website: FETCH_DEPENDS PATCH_DEPENDS EXTRACT_DEPENDS USES More information on these fields can be
Fetch, Patch, & Extract dependencies and Uses Read More »
Today, kwm mentioned that http://www.freshports.org/Mk/bsd.port.mk was out of date, showing the most recent commit as back in March. My first concern was the system had stopped recording such commits. To check on that, I looked at https://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk and searched my email for the most recent commit message. Extracting the message id from that email, I
cache invalidation Read More »
Tonight I started doing some database structure changes for branches. I thought: Hopefully nobody commits to two branches at once. Yes. They do. Oh oh. mat gave me a few examples: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=758626+0+current/svn-src-all http://docs.freebsd.org/cgi/getmsg.cgi?fetch=747218+0+current/svn-src-all http://docs.freebsd.org/cgi/getmsg.cgi?fetch=735782+0+current/svn-src-all Look at those URLs and you’ll see: Changes in other areas also in this revision. The code already ignores everything after
Commits to multiple branches Read More »
What do you want out of FreshPorts? You want to know: What is available What version Any notes in UPGRADING Any vulnerabilities You want to know about this for HEAD and for RELENG_9_1_0. You want to know that on HEAD, sysutils/bacula-server is version 5.2.12_3, but on head, it’s 5.2.12. That’s important. That’s commit history. FreshPorts
What branches means to FreshPorts Read More »
Yesterday, I wrote about some great progress on getting FreshPorts to work with multiple repositories to cater for the branches of the FreeBSD ports tree. At the end of that post, I talked briefly about wanting global settings or variables for my stored procedures. Shortly after posting that, I found a solution in the form
Session variables! Almost. Not quite. Read More »
I just realized (although, deep in the recesses of my innocent mind, I suspect I knew) that FreshPorts will require one repo for each branch. The email on the svn ports branches mailing list includes multiple branches. A quick glance around the archives finds me these branches: RELENG_9_1_0 RELENG_9_2_0 2014Q1 I know there will be
Multiple branches, multiple repos Read More »