In this post I’ll talk about how the code intially took the easy way out and how recent changes have tightened that up. In short, the code would raise N messages when just a single notification is sufficient. Today the full vuxml database was reloaded into FreshPorts. This affects approximately 3454 ports and the marking […]
Changing how we record ports which need cache clearing Read More »
FreshPorts can display a single commit based upon commit id, which is based upon the Message-Id of the commit email (for subversion and cvs) or the commit hash (for git). Commit ids are specified in the URL. Cached entries are stored on disk and are named after the commit. It is because are are using
Changing cache file name for commits Read More »
This documents the git specific code which I need to package and deploy. /usr/local/libexec/freshports This is installed by freshports-scripts-git, and I have the directory symlinked to ~/scripts on devgit.freshports.org for convenience. In this directory, we have the following symlinks to other directories: Ignoring lines 2 and 4 which are not relevant, we have this list
packaging up the git-specific code Read More »
This post documents the database upgrade process. Issues encountered during initial attempts There are permission issues on the database. Not everything is owned by the postgres super-user. In fact, many of them are owned by dan – this database is 20+ years old. To easily resolve the ownership issue, I take the database dump (named
git: database upgrade process Read More »