Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Oct 2000 03:04:18 -0800
From:      jay.krell@cornell.edu
To:        "Mike Meyer" <mwm@mired.org>
Cc:        <questions@freebsd.org>
Subject:   Re: make install multiprocess safe?
Message-ID:  <005601c04261$278b10a0$8001a8c0@jayk3.jaykhome>

next in thread | raw e-mail | index | archive | help
I'm still a while away from understanding that stuff.. maybe if it was C or
C++..

 - Jay

-----Original Message-----
From: Mike Meyer <mwm@mired.org>
To: jay.krell@cornell.edu <jay.krell@cornell.edu>
Cc: questions@freebsd.org <questions@freebsd.org>
Date: Monday, October 30, 2000 1:47 AM
Subject: Re: make install multiprocess safe?


>jay.krell@cornell.edu types:
>> Imho it should be more safe.
>> Even concurrent builds in the same directory should work better -- one
>> should notice the other and either wait or abort.
>
>Well, once you patch the files in /usr/ports/Mk to do that, use
>send-pr to submit them.
>
> <mike
>
>>  ..Jay
>>
>> -----Original Message-----
>> From: Mike Meyer <mwm@mired.org>
>> To: jay.krell@cornell.edu <jay.krell@cornell.edu>
>> Cc: questions@freebsd.org <questions@freebsd.org>
>> Date: Sunday, October 29, 2000 11:31 AM
>> Subject: Re: make install multiprocess safe?
>>
>>
>> >jay.krell@cornell.edu writes:
>> >> This has been bugging me a while. I've always just avoided it.
>> >> Is it safe to
>> >>     cd /usr/ports/1/2
>> >>     make install &
>> >>     cd /usr/ports/3/4
>> >>     make install
>> >> ?
>> >
>> >Mostly it's safe.
>> >
>> >> if both go to like register the package at about the same time, will
the
>> >> package database stay not corrupted?
>> >
>> >The "packages database" is a collection of flat text files. You only
>> >get into problems if you try writing to the same one at the same time.
>> >
>> >> I'm assuming both have all their dependents installed or they share no
>> >> dependents -- to avoid the question of building in the same directory
at
>> the
>> >> sam etime.
>> >
>> >*That's* the real problem: dependencies. If both ports depend on the
>> >same third package, and they both start writing on the +REQUIRED_BY
>> >file at the same time, it could mess up that file. On the other hand -
>> >that's not a major breakage; it just means that you don't get warned
>> >about all the dependencies when you remove the third package. As
>> >opposed to what happens when the two makes start trying to build the
>> >same package, which tends to break that build.
>> >
>> >If no package in system is directly required by more than one unbuilt
>> >package in the tree of dependents, you will be safe. Given that all
>> >the dependents of the two ports are built, this means that no package
>> >is directly required by both ports.
>> >
>> > <mike
>>
>>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005601c04261$278b10a0$8001a8c0>