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 »
Over the past few weeks, I’ve made some progress towards supporting the branches for FreshPorts. Today, I started making the first code changes and I wanted to share that with you as I went along. Finding the messages FreshPorts processes commits by parsing the messages from the mailing list. I think it might be feasible
Processing the first port commit from svn-ports-branches 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 »