When a new repo is imported, the packages cache needs to be deleted. The cache is on the front-end, the web server. Cache clearing on the web server is handled by the fp-listen daemon. It does this by using the LISTEN command. The list of channels it listens to is controlled by the listen_for table: […]
Clearing the packages cache Read More »
Today, while I wasn’t looking, both dev and test located and imported new package information for: FreeBSD:11:amd64 FreeBSD:11:i386 FreeBSD:12:amd64 FreeBSD:12:i386 FreeBSD:13:amd64 FreeBSD:13:i386 However, the packages table was not correctly updated. Why? Because I lost some function code I wrote. This is the code which was in use, as mentioned in Using DEFERRABLE INITIALLY DEFERRED on
Found new repo release – automatically imported it Read More »
A new FreshPorts features is being developed. I’m trying to determine if packages for a port can be cached separately from the port itself. I will explain. When you visit a port page, if it’s not cached, the page is built and then cached. Not the whole page, just the parts pertaining to that port.
In the previous post I documented how the packages_raw table is updated to populate the abi_id and port_id columns. This post will discuss how that data is then pushed into the packages table. Thoughts When updates arrive, they arrive in quantity. The latest update was 30474 records. From that, we will have some new packages,
Updating the packages table – INSERT, UPDATE, DELETE – plus some ZFS configuration Read More »
This post is another in the packages series. It documents how the data is transformed from the raw form (packages_raw) into normalized data (packages). The Packages – how is this data stored? post may be useful reading. The primary purpose of this blog post is documentation of the above mentioned transformation process. Along the way
Using DEFERRABLE INITIALLY DEFERRED on constraints Read More »
This is the latest in a series of posts dealing with displaying what packages are available for a given FreeBSD port. The Packages – how is this data stored? post may help you follow along. It outlines the data and the tables used in this post. Last night I managed to get the right data
Procedural vs query approaches Read More »
This post documents what I recently put into a gist on Github. It should serve as a rough introduction to how FreshPorts handles packages extracted from packagesite.yaml files. All the platforms These are the plaforms (also known as ABI) for which we are monitoring packages created by the FreeBSD project. They relate to URLs found
Packages – how is this data stored? Read More »
Since the last past, I’ve added quarterly packages to the system. I want to outline the changes while I remember the. I will start by outline the tables we have. abi The abi table contains the usual suspects. Entries in this table are added manually, when a new release comes out. See https://pkg.freebsd.org for examples
Packages for latest and quarterly Read More »
This post deals with adding a new feature: A table of which FreeBSD version and architecture has a given package The goal: parse the packagesite.yaml supplied with each repo and load the results into the FreshPorts database. A bunch of the background in the above URL, and I don’t want to repeat it here. This
What packages are now available for this port? Read More »