Comments on: MASTERPORT : who uses it?

By: Dan Langille

Dan Langille — Fri, 12 Oct 2007 14:58:51 +0000

After running set-master-port.pl, the master port for each port is correctly set. Then, I ran refresh-slave-ports.pl to refresh all the slave ports based on the current master port definitions. This needed to be done because all slave ports are updated automatically after a commit to a master port. Since master/slave relationships were not correct in the database, this last step was required to get things up to date. One relationship was missed in all this: I needed to clear the cache for each master port. Each master port lists all the slave ports. Similarly, each slave port list its master port. Rather than code a solution, I did this:

SELECT DISTINCT('rm -rf /usr/websites/freshports.org/dynamic/caching/cache/ports/' 
|| master_port || '/*') FROM ports_active WHERE master_port <> '';

The resulting output became a shell script, which cleared out the cache. More about this in the next article.

By: Dan Langille

Dan Langille — Fri, 12 Oct 2007 09:47:49 +0000

The fix may be as simple as:

$ cvs di port.pm
Index: port.pm
===================================================================
RCS file: /home/repositories/freshports-1/scripts/port.pm,v
retrieving revision 1.43
diff -r1.43 port.pm
534a535,536
>
> $master_port =~ s|$FreshPorts::Config::path_to_ports/||;
$

I’m running the Verify/set-master-port.pl script now.

By: Dan Langille

Dan Langille — Thu, 11 Oct 2007 23:30:35 +0000

I now think this problem can be solved with a simple string match and optional removal. In which case, the problem goes away entirely.