On 11 Apr 2013 14:48, "Vitaly Magerya" wrote:
>
> Earlier I wrote:
> > Anyway, the problem you're describing allows for another fix. If ports/A
> > depends of file-B, port system could check not only that file-B exists,
> > but if there is also a package that installed it (via 'pkg which'), and
>
Earlier I wrote:
> Anyway, the problem you're describing allows for another fix. If ports/A
> depends of file-B, port system could check not only that file-B exists,
> but if there is also a package that installed it (via 'pkg which'), and
> if not, install ports/B. This will of course slow down po
Matthias Apitz wrote:
> 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 be
On Thu, 11 Apr 2013 11:36:54 +0100
Chris Rees articulated:
> 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.
Unless yo
On 11 April 2013 11:19, Matthias Apitz 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 installa
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,
