On 11 April 2013 11:19, Matthias Apitz <g...@unixarea.de> wrote: > > Hi, > > Sometimes, while compiling all my ports, I encounter the following > problem: > > Say, we are installing ports/A which depends on ports/B; the Makefile > detects the dependency and goes to install ports/B; if now during the > final installation process, some files are already delivered to > /usr/local, some files not, the system goes down (by intention because > it's time to go out), before the installation of ports/B is fully done > and registered to /var/db/pkg, next time when you restart installing > ports/A it often sees, because the file referenced in the Makefile > was allready installed (while others not), it thinks that ports/B was > installed fine and proceeds with ports/A which later (or even in some > other area) gives an error due to missing files of ports/B; > > I think, the only solution is that the dependency is not only based on > some (random) file of B, but on the fact if B was *fully* installed and > registered in /var/db/pkg; > > comments?
Installing a port isn't atomic by definition; the larger ones have loads of files that need installed. If I read your description carefully, your solution is to simply avoid interrupting during the installation phase. Chris _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"