Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 35441 - Portage shouldn't allow you to do simultaneous emerges
Summary: Portage shouldn't allow you to do simultaneous emerges
Status: RESOLVED WORKSFORME
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-09 06:35 UTC by ferret
Modified: 2011-10-30 22:38 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ferret 2003-12-09 06:35:43 UTC
I'm constantly told simultaneous emerging is bad, even emerge on one terminal and
emerge --fetch on another screws up (but see bug 1661 and bug 33098).

Is there any good reason emerge should *let* users do parallel emerges? Why not
stop them using some simple lockfile system? Sure, some people want to risk it
occasionally and emerge one small tiny unrelated thing alongside their big, time
consuming xfree emerge, but there could be ways around that (a get-around var in
/etc/make.conf, another command line option, a big red warning message when
simultaneous emerge is attempted, but without actually preventing the user from
doing it).

Of course, if this were actually implemented you'd have to be careful to allow
emerge -s, emerge -S and emerge -p.

Any thoughts?
Comment 1 Nicholas Jones (RETIRED) gentoo-dev 2003-12-09 17:35:29 UTC
It should be ok in current stable portages as lockfiles are now
employed on the database. Worst thing that will happen is deletion
of the source code being compiled.

It's being worked on.
Comment 2 Petteri Räty (RETIRED) gentoo-dev 2011-02-12 20:22:02 UTC
*** Bug 354419 has been marked as a duplicate of this bug. ***