| View previous topic :: View next topic |
| Author |
Message |
sschlueter Guru

Joined: 26 Jul 2002 Posts: 578 Location: Dortmund, Germany
|
Posted: Thu May 29, 2003 1:19 am Post subject: emerge: separate compile and install |
|
|
Is there a way to tell emerge to compile a package but not immediately install it? I already know "emerge -B" but that can't handle dependencies.
The reason why I want to do this is that I have experienced strange things happening when updating a package while the application/daemon/whatever was running.
Let's say I want to upgrade KDE from 3.1.1a to 3.1.2. Of course compiling takes a lot of time and I still want to use KDE during that period of time. If I simply type "emerge kde", the system will become somewhat inconsistent during different periods of time (kdelibs already updated but none of the apps, app running but the binary got already overwritten with the new version, ...)
So I think I want to compile the packages and not installing them, and then shutting down the daemon/logging out of KDE/going single user/etc. and install the packages and restart the daemon/start using KDE again/going multiuser/etc.
The problem is that e.g. "emerge -B kde" doesn't work because of the dependencies. Is there a different possibility?
(I know that I could build the tbz2 files on a different machine but that's not an options for me right know.)
Thanks for your help  |
|
| Back to top |
|
 |
cyfred Retired Dev

Joined: 23 Aug 2002 Posts: 596
|
Posted: Thu May 29, 2003 10:50 am Post subject: |
|
|
Have a look at the ebuild command.
ebuild <foo.ebuild> {unpack,compile,install,etc...}
man ebuild |
|
| Back to top |
|
 |
sschlueter Guru

Joined: 26 Jul 2002 Posts: 578 Location: Dortmund, Germany
|
Posted: Fri May 30, 2003 5:12 am Post subject: |
|
|
| cyfred wrote: | Have a look at the ebuild command.
ebuild <foo.ebuild> {unpack,compile,install,etc...}
man ebuild |
I also know the ebuild command. But it doesn't solve the problem either because it completely ignores the dependencies. This is even worse.
Just in case I haven't made clear what the problem actually is (English is not my native language), here's an example:
I want to emerge xine:
| Code: | #emerge -p xine-ui
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild U ] media-libs/xine-lib-1_beta12 [1_beta11]
[ebuild U ] media-video/xine-ui-0.9.21 [0.9.20] |
| Code: | #emerge -B xine-ui
Calculating dependencies ...done!
!!! --buildpkgonly requires all dependencies to be merged.
!!! Cannot merge requested packages. Merge deps and try again. |
So I would have to emerge xine-lib, install it and emerge xine-ui and install it. But I don't want multiple installation procedures but just one. BTW, xine is a pretty simple example - it would take 3 or 4 installation procedures when upgrading KDE. |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|