Hello Mathias
I am way behind on my mail lists so hopefully this reaches you in time
to still be relevant.
The other responses to your question have covered the technical aspects
involved with installing KDE and generally any package in Fink. There
is no way that I can improve on their description of the mechanics of
how installs are accomplished so my only comment there is " ya! what
they said." What may be of use to you however is some of the
considerations that affect me in my context.
I run 10.3.9 on a 500Mhz G3 iBook. It was hopelessly under powered when
it shipped so I upgraded to 640MB of RAM and a 60GB hard drive. With
that configuration, installation of packages can take a long time. When
Ben upgrades the KDE distribution and if I have not run Fink in the
last week or two I can see around 300 packages that need to be
installed or upgraded. On my machine that translates to Fink going away
for around five days. Fink builds and compiles 24/7 but it happens in
the background (ie. I run other applications in the mean time.) Other
than a bit of a performance hit I do not notice it. If I switch to
tcsh ( this does not seem to work in bash) I can even run Fink in two
different terminal windows or in FinkCommander at the same time. This
good for simple stuff like 'fink info' but I would not try cleanup or
install while either of them is running somewhere else.
What I do to help the situation is leave everything installed. I run
'fink cleanup' to get rid of the temporary or obsolete files but other
than that if Fink installs it I leave it. The reason being, if I run
'fink selfupdate' and 'fink update-all' daily or close to it I do not
get hit so bad with the big installs. If the build dependencies are
already on my hard drive I do not have to wait for them to build or
install every time a package that depends on them gets upgraded. Also
if I leave it too long between updates then a lot of things change and
I have to wait for everything. Further to that, the more packages that
get installed or upgraded at one time the more likely Fink is going to
run into conflicts and then you have to restart the update. If it
happens during the night then I lose whatever build and compile time
that elapses between the conflict and when I check my machine next.
I do not know how much of an effect reloading and rebuilding will have
on your situation but for me it seems to be far more efficient to just
let Fink put in what it needs and leave it alone. At this point I would
not even consider deleting something that might get reused. Not only
that but I save whatever time it takes to go through the dependecies to
discover what is not needed and then delete it. This may be an approach
to consider for yourself.
Cheers
Lorenz
On 10 Nov, 2005, at 7:16 AM, Alexander K. Hansen wrote:
On 11/10/05, matz.org <[EMAIL PROTECTED]> wrote:
thanks for your answers!
so, what do you suggest to do?
just say "yes" and install all that stuff or is there an alternative
way to avoid the installations of all that packages?
"That, and the most stable by far of the output backends amarok has at
it's disposal is GStreamer, which is a gnome framework and brings in a
*ton* of gnome dependencies." what do you mean benjamine?
so you say that i can remove all "fink dumpinfo -f Depends amarok"
output packages, right? since i see that fink will install 184
packages, is there a way to feed fink with that list of packeges to
unistall?
thanks for your help!
mathias
You don't want to use -fdepends in this case. (Dan should know better
:-) )
You want to use -fbuilddepends, since that will give you the packages
that were required to build amarok, but not to run it.
There's not a builtin way to feed fink that list, unfortunately.
However, the debfoster package does provide a way to let you go
through and see what packages don't have anything that depends on
them--some will be build dependencies and some will be top-level
packages (e.g. those with user-level executables).
--
Alexander K. Hansen
Fink Documenter
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
