On Thursday, July 10, 2003, at 08:36 PM, John Davidorff Pell wrote:
Has anyone done any work with making fink a little more friendly if I
run multiple instances of it? iLike to have more than one compile
going at a time, but on occasion I'll find that I started compiling
foo and then want to compile bar which depends (not build depends) on
foo and it'll delete the foo build folder which destroys the work that
had already been done. I'm thinking a simple lock file would be
perfect, with the PID of the fink process that started it as its
contents. any ideas?
If bar depends on foo, it also builddepends on foo. Sorry :-)
Even when there's no direct dependency, it's always risky to run
multiple finks at once. Dpkg simply refuses to run multiple instances,
so that gets in the way. More importantly, one compile could end up
changing or removing files the other compile needs, which may make the
compile fail, or may give you some very hard-to-find bugs.
If you're really intent on running multiple compiles at once, you can
always install fink multiple times in different prefixes :-)
Also, I think (for the future) that it would be very useful to
developers to be able to see the dependancy tree for foo instead of
just that foo depends on something which depends on dlcompat and
glib2. am i making sense?
Try package pkg-order in unstable. Commands pkg-revdeps and pkg-deptree
are probably what you want.
Dave
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
|
