What’s in the pipeline, how it works, how it’s made…
FreshPorts has always strived to be correct. Even when it’s difficult. One issue which always always proven difficult is ports that rely upon other ports. or cannot be installed with other ports. Case in point, sysutils/msktutil, which includes this message: IGNORE: cannot install: SASL support requested and openldap-client-2.4.20 is installed That’s not really appropriate on […]
Getting more accurate results… Read More »
FreshPorts processes commit emails, updates via svn, then extracts data via make -V. That’s the short of it. However, stuff goes wrong. And sometimes we can’t update. Or the extract fails. This leaves data in the database which does not reflect what is in the port. This query, which I was creating tonight, may help
What ports need to be refreshed? Read More »
Why can’t things be simple? The basic premise of FreshPorts is parse, an email, put it in the database. Sounds simple? Well, it is. Until you start dealing with the exceptions. Such as slave ports. Such as UTF-8…. I only just got used to dealing with base64-encoded messages when a real UTF-8 character shows up.
Why can’t things be simple? Read More »
I think I have a solution for base64 emails. I emailed Matthew Seaman on Wednesday about this issue. He put me onto two very useful Perl modules: Email::MIME mail/p5-Email-MIME Email::Simple mail/p5-Email-Simple/ Email::Simple::Header The solution is coded below: sub myGetMessage { my ($message); my ($encoding); while () { $message .= $_; } $encoding = myGetMessage_ContentTransferEncoding($message); print
Solution found for base64 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 »