I was just creating a new jail for working on git & FreshPorts. I was intrigued to see that iocage uses send | receive to create the new jail: [dan@slocum:~] $ ps auwwx | grep iocage root 64166 3.7 0.0 12788 4036 1 D+ 21:16 0:06.10 zfs send system/iocage/releases/12.0-RELEASE/root@git-dev root 64167 2.8 0.0 12752 4036 […]
Creating the first FreshPorts git-specific jail Read More »
We have the first commit process via git into FreshPorts. Details in this git comment. Work remaining: check out that commit into the working copy of the files run make -V on the working copy to get the refreshed values for the port[s] affected by this commit The 2nd part – very little code change.
first commit process via git Read More »
I want to move FreshPorts towards using commit hooks and away from depending upon incoming emails for processing new commits. Much of the following came from a recent Twitter post. You might think: why are we using emails? Why? Because we can. They were the easiest and most simple approach. It is a time-proven solution.
Moving towards commit hooks Read More »
I’m trying to think of a list of things that FreshPorts can do which might be useful. I can think of these: provides example dependency line. e.g. p5-XML-RSS>0:textproc/p5-XML-RSS list of dependencies for a port list of ports depending upon this port Default configuration options what packages install a given file (e.g. bin/unzip) what ports does
Things you didn’t know FreshPorts can do Read More »
When the time comes, and the FreeBSD project is using git, there will be work to be done on FreshPorts. If the commit emails are similar to those under cvs and svn, it should be straight forward to parse the email and convert it to XML. Once the data is in XML, the commit can
git and FreshPorts Read More »