Another snag: devel/doxygen and audio/jack seem to have themselves as dependencies

[Thomas Mueller]

I have hit another snag in updating ports that depend on png. 

Portmaster seems to go into an infinite loop or keep looking for a long time, producing monstrous log files:


-rw-r--r--  1 root  wheel      72138 Oct  2 03:18 /BETA1/usr/ports/build-png.log
-rw-r--r--  1 root  wheel       8060 Oct 19 02:36 /BETA1/usr/ports/build2.cmd
-rw-r--r--  1 root  wheel     351911 Oct 19 02:37 /BETA1/usr/ports/build2.log
-rw-r--r--  1 root  wheel       8052 Oct 19 02:41 /BETA1/usr/ports/build2b.cmd
-rw-r--r--  1 root  wheel       8063 Oct 20 03:47 /BETA1/usr/ports/build3.cmd
-rw-r--r--  1 root  wheel     377896 Oct 19 02:50 /BETA1/usr/ports/build3.log
-rw-r--r--  1 root  wheel       7913 Oct 20 04:42 /BETA1/usr/ports/build4.cmd
-rw-r--r--  1 root  wheel    2573873 Oct 20 04:15 /BETA1/usr/ports/build4.log
-rw-r--r--  1 root  wheel       7186 Oct 21 04:45 /BETA1/usr/ports/build5.cmd
-rw-r--r--  1 root  wheel   13451651 Oct 20 07:37 /BETA1/usr/ports/build5.log
-rw-r--r--  1 root  wheel       7150 Oct 25 07:07 /BETA1/usr/ports/build6.cmd
-rw-r--r--  1 root  wheel  757204321 Oct 25 03:04 /BETA1/usr/ports/build6.log
-rw-r--r--  1 root  wheel  129655234 Oct 25 07:18 /BETA1/usr/ports/build7.log

That last one, build7.log, only took ten minutes to get that large!

Logs, too big to post here, suggest a dependency loop, and I ran 
make all-depends-list | more
in both devel/doxygen and audio/jack directories, and the result for devel/doxygen showed devel/doxygen, the result for audio/jack showed audio/jack .

I also tried 
make all-depends-list | more 
in print/hplip directory, and print/hplip did not show.

I remember a circular dependency bug in the recent past with devel/doxygen and audio/jack, so that's where I looked, especially after finding these ports repeatedly in my monster-sized logs.

Portmaster, when it fails, ends the log with a note to resume by running
portmaster <flags> <list of ports separated by spaces, all on one line>.

So I separate out that part and edit as necessary with vi:  that's how I got my 
build?.cmd files.

Tom