Then ^c and add/remove what you need.
On Jan 26, 2011 1:30 PM, "PK" wrote:
>>
>> Don't use multiple instances of emerge, they'll probably all try to merge
>> the same dependencies. Do it the way the portage developers intended, use
>> the --jobs option with a single emerge instance.
>>
>>
> Sure,
>
> Don't use multiple instances of emerge, they'll probably all try to merge
> the same dependencies. Do it the way the portage developers intended, use
> the --jobs option with a single emerge instance.
>
>
Sure, but sometimes while emerge is building a bunch of packages I remember
that I've forg
On Wed, 26 Jan 2011 12:12:57 +, PK wrote:
> Is there any way to simultaneously emerge multiple packages (multiple
> instances of 'emerge') that share common dependencies ?
Don't use multiple instances of emerge, they'll probably all try to merge
the same dependencies. Do it the way the portag
On Wed, Jan 26, 2011 at 2:12 PM, PK wrote:
>
> Hi,
> Is there any way to simultaneously emerge multiple packages (multiple
> instances of 'emerge') that share common dependencies ?
> I'm aware that portage uses locking mechanism before modifying 'world' file,
> but what about the actual building
Hi,
Is there any way to simultaneously emerge multiple packages (multiple
instances of 'emerge') that share common dependencies ?
I'm aware that portage uses locking mechanism before modifying 'world' file,
but what about the actual building process ? I'd expect emerge to check if
dependency pack
5 matches
Mail list logo
