On 22/3/02 3:47 PM, "Steven Burr" <[EMAIL PROTECTED]> wrote:

> 
> On Thursday, March 21, 2002, at 07:38 AM, Max Horn wrote:
> 
>> Seems as if Preferences.nib is missing from CVS, I can't compile it
>> without that.
> 
> Sorry.  I ran into the same problem when I did a test run on my kids'
> Mac and thought I had fixed it.
> 
> I think the repository is in good shape now.  I committed the
> Preferences.nib contents, deleted the old version of FC from the other
> Mac and did another test run with anonymous cvs.  FC compiled and ran
> several commands, including selfupdate-cvs.    As I write this on my
> iBook, FC is running update-all without any problem (so far).
> 
> SourceForge has already removed the build directory.  I took  Finlay's
> advice and selected an alternative local directory for the build and
> build intermediates in PB preferences.
> 
> Thanks for all the help.

I had a look at FinkCommander, and it looks very promising!

One suggestion that I have, though... Perhaps when you click on the name of
a package, the program should show the information immediately, instead of
having to go to 'Source -> Describe'. This may take some tweaking on Fink's
behalf, though... As it sometimes takes a while for Fink to retrieve the
information.

Perhaps parsing the info returned by 'fink describe <package>' would also be
useful. Some users probably don't want to view the information in DescPort,
DescPackaging and DescUsage, so maybe there should be an option to somehow
only include the DescDetail field in the bottom pane. (I'm not sure how this
would be done, though... Fink doesn't label the fields in its output...) You
could then have an option somewhere to increase or descrease the amount of
information given for packages (like you can do with dselect... Press 'I'
with a package selected and it will switch between different levels of
information.)

One thing that might also be nice is to display the dependencies of a
package. (Again, not by default... Perhaps on a different 'level'), but as
Fink currently doesn't output this information in 'fink describe', that
would be a bit difficult...

[Turned out to be a bit more than one suggestion... Oh well! :) ]

Hope this helps!

Thanks!


_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to