On Saturday 18 October 2003 06:58 am, Stephen Liu wrote:
> Hi all folks,
>
> I have been running installation of KDE for 36+ hours and still
> could not see my shore ahead. Those pre-compile packages on CD2
> seems not helpful.
>
> I ran
> # emerge sync
> then
> # emerge -k kde
>
> it indicated 60 packages to be installed. But most time I saw it
> downloading packages from Gentoo website. Last time, about 3 hours
> ago, I saw 33/60 packages being downloaded. The download time took
> about 3 minutes but the compilation took lengthy time.
>
> If accidentally the PC is interrupted can I re-do KDE installation
> without starting from the beginning. If YES then HOW.
>
> Another problem is Xwindow can't be started which has been posted
> in my previous email. In the worst case can I re-do installation
> of xfree without starting from the very beginning, skipping those
> packages already installed?
>
> Kindly advise. Thanks in advance.
>
> B.R.
> Stephen
>
>
> --
> [EMAIL PROTECTED] mailing list
The kde build does seem a bit slow, though you are making progress.
Yes, if the build is interupted, you can start from where you left
off by simply issuing the command "emerge kde" It will start with the
package it was working on when interupted.
After you emerged xfree. if you had done "startx" you probably would
have seen an ugly grey screen with an "X" in the middle that would
move with your mouse. This is normal and indicates success. Xfree it
self has no window manager and, by itself is pretty much useless.
I've never used the precompiled packages so I can't help with why
your machine is building everything from source. Perhaps "emerge
can't find the packages on your harddrive?
From man emerge:
--usepkg (-k)
Tells emerge to use binary packages (from
$PKGDIR) if they are available, thus possi-
bly avoiding some time-consuming compiles.
This option is useful for CD installs; you
can export PKGDIR=/mnt/cdrom/packages and
then use this option to have emerge "pull"
binary packages from the CD in order to sat-
isfy dependencies.
--usepkgonly (-K)
Behaves just as --usepkg except that this
will only emerge binary packages. All the
binary packages must be available at the
time of dependency calculation or emerge
will simply abort.
If I were you, I would interupt the build at a point where it has
just finished a pachage and restart it using the --usepkgonly (-K)
option. If this fails, portage cannot locate the packages and you'll
have to look back through the instructions to find where you should
have them. At that point you have the choice to either fix the
package directory or continue as you have been. The advantage in
continuing as you are now is that you will have the latest packages
merged and updating will be much quicker.
Another glitch I just thought of is that you may not be able to merge
precompiled packages at this point as they will conflict with later
versions you have built from source.
--
Regards, Ernie
100% Microsoft and Intel free
--
[EMAIL PROTECTED] mailing list
