Date: Thu, 11 Apr 2013 11:36:54 +0100 From: Chris Rees <crees@FreeBSD.org> To: Matthias Apitz <guru@unixarea.de> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: problems with half installed ports Message-ID: <CADLo83_1jL9o6dP5sO9eGjF=McfB_gVJeXCNLHT46w8YMjxiEg@mail.gmail.com> In-Reply-To: <20130411101916.GA3339@tinyCurrent> References: <20130411101916.GA3339@tinyCurrent>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 April 2013 11:19, Matthias Apitz <guru@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_1jL9o6dP5sO9eGjF=McfB_gVJeXCNLHT46w8YMjxiEg>