I have to say, FreshPorts would be a very simple piece of code if it wasn’t for all the exceptions to the rules. But then, that is true for most software. Case in point, I’ve seen three base64 encoded emails in the past week or so. Each one makes FreshPorts barf. It has no idea […]
base64 encoded emails Read More »
In the past few days, I have implemented the full pathnames solution on dev. It was first implemented on gelt, a server setup explicitly for developing full pathnames. I am so glad that I keep notes when making changes such as this. Sometimes it is days or weeks between testing out a new approach and
Full path names now on dev Read More »
I noticed just now that the database has not been keeping up with the rapid changes to the incoming XML. In general, anything in the XML should eventually get into the database. That is just not happening. Case in port: repo name. This is now becoming an issue when we link to the SVN repository.
Creating the repo table Read More »
I think the work to move to full pathnames is proceeding well. I created another website, gelt.freshports.org, and I’m doing all the work over there. What I learn and the code changes will eventually be applied to the other websites. The differences should be subtle, and barely noticeable. Most of the changes are internal. Compare
Get your full path names here! Read More »
Before the last post was published, I forgot to add in the fix for the pathname problem. freshports.org=# select ElementPathnameUpdateChildren(453745); It run. A long time. I let it run. For hours. About 16 hours. Then I killed it. I checked the procedure. It made sense. Then I checked the update statement: freshports.org=# explain analyse UPDATE
An index can make all the difference Read More »
I started looking at how to create these new directories as mentioned yesterday. This starts the process: $ psql freshports.org psql (9.0.8, server 9.0.9) Type “help” for help. freshports.org=# select Element_Add(‘/base/head’, ‘D’); element_add ————- 453742 (1 row) freshports.org=# select Element_Add(‘/doc/head’, ‘D’); element_add ————- 453743 (1 row) freshports.org=# select Element_Add(‘/ports/head’, ‘D’); element_add ————- 0 (1 row)
Creating the new repo base directories 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 »
Wesley Shields (wxs@) wrote in to point out that the commits for Mk/bsd.sites.mk where not showing up correctly. Not sure if you know about this or not but it appears that (at least) Mk/bsd.sites.mk is not being properly updated on freshports since August 5. I compared these two URLS: http://www.freshports.org/Mk/bsd.sites.mk http://dev.freshports.org/Mk/bsd.sites.mk Yep. The full commits
Wrong path on src commits Read More »
FreshPorts has a web page caching issue for all non-port commits. This also affects commits in the ports tree that do not touch a port. e.g. Mk, Tools, etc. I hope to fix it later this week. dev does not have this problem. beta & www do.
HEAD UP: caching problems Read More »
Hmmm, I thought with my recent changes to use ‘svn up -r XXX’ would solve the problem of repo-copies. Why are repo-copies a problem for FreshPorts? FreshPorts knows only about the files mentioned in a commit. With repo-copies, a whole directory is moved, but the files in that directory are not mentioned in the commit.
svn up creates conflicts Read More »