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 »
Today I managed to make quite a bit of progress trying to incorporate multiple ports trees into the commit processing. The diff is about 985 lines long. It’s not as complex as it sounds. I just have to pass $CommitBranch around to various functions. The result: I have the commits going into the database, but
Multiple repos – good progress Read More »
In a recent post, I said: That second patch uses the same string you saw above in the previous patch. Yes, it would be better to have added that string to just one place. I welcome patches for that change. Today I will show you that code. With help from Matthias Andree on IRC, I
Adding code, removing more code to reduce duplication Read More »
As mentioned in my previous post, if FreshPorts is to display commits from every branch, it is going to need one check-out of each branch of the ports tree. Tonight I started looking into that and hit a snag in an unexpected area: name length. I do most of my development work from within jails.
Multiple ports trees for FreshPorts Read More »
I recently wrote about a problem with FreshPorts not tracking changes by branch. I recently patched the dev system and things are looking better. The patch is: This change forces the code to look for an existing row in the system_branch_element_revision table, and if not found, add it in. I used this commit against news/trn4
Tracking port changes by branch – first fix Read More »
It’s pretty easy to say that there’s just one branch for the FreeBSD ports tree. And it’s not really a branch at all. Commits were done to HEAD, and branches were ignored. That has recently changed. The FreeBSD ports tree will be branched every three months and commits to that branch will be tightly controlled.
Tracking port changes by branch Read More »
We learn as we go. We create new designs based on past experiences and knowledge to date. Back when FreshPorts started, we catered only for ports. Now we cover the ports and src trees. Now that we are on svn, we can do much more than when on cvs. One change I would like to
going to full pathnames Read More »