On Saturday, Dec 28, 2002, at 06:13 US/Eastern, Martin Costabel wrote:
Bill Bumgarner wrote:
[]
Yes-- but the default for Fink is not to do that and I would bet that most of the users that use selfupdate-cvs have no CLUE about ~/.cvsrc. The default for Fink should be to spew only the information that is actually informative-- the current behavior does not do that.
As you'll note, I added -q to the cvs command in fink -- everything from the pipe on could be deleted.
The -q would be easy to implement in function of the verbosity_level, similarly to the unpack_cmd in SelfUpdate.pm. No objections here.
I don't see the point of making it anything but the behavior all the time. The 'updating directory' stuff coming out of CVS is purely noise; I have never run across a situation where it is useful or a developer that isn't grateful to learn how to make it go away.

Tieing yet more stuff to the verbosity_level will make it more likely that more people will not be able to find a verbosity_level that is to their liking or current needs.

A new patch:

Index: perlmod/Fink/SelfUpdate.pm
===================================================================
RCS file: /cvsroot/fink/fink/perlmod/Fink/SelfUpdate.pm,v
retrieving revision 1.24
diff -r1.24 SelfUpdate.pm
336c336
< $cmd = "cvs -z3 update -d -P";
---
> $cmd = "cvs -q -z3 update -d -P";

With the patch, I now see the following on a selfupdate-cvs (with no packages changed in the repository):

su bbum -c 'cvs -q -z3 update -d -P'
? .DS_Store
? stamp-rel-0.4.0
Reading package info...

Not true -- the default Fink installation will spew a '? ' line for every package in the OS X 10.1 tree on 10.2. At least, this has always been the case for me and I never touch anything in the Fink tree outside os the local/ tree and-- very occasionally-- using inject.pl to inject a custom Fink feature.
If this is true, it's a bug in the upgrade procedure you used. I cannot believe it is really "every package" in 10.1. Aren't these only very old packages that are no longer even in 10.1 cvs? Usually this happens when your CVS/Entries files get out of sync with what you have on the disk, because they were updated somehow differently than with the "cvs update" command. But then all the files marked with a "?" are obsolete anyway and can (and should) be deleted.
This has happened on every fink installation I have ever done-- many, many times. I have followed the instructions to the letter on the 'install on Jaguar' guide and 'fink selfupdate-cvs' has always produced a huge slew of the "? ..."

I.e.:

The 'su' command will be used to run the cvs command as the user 'bbum'.
After that, the core packages will be updated right away; you should then
update the other packages using commands like 'fink update-all'.

su bbum -c 'cvs -z3 update -d -P'
? .DS_Store
? stamp-rel-0.4.0
? 10.1/stable/crypto/finkinfo/curl-ssl-7.9.2-2.info
? 10.1/stable/crypto/finkinfo/egd-0.8-1.info
? 10.1/stable/crypto/finkinfo/egd-0.8-1.patch
? 10.1/stable/crypto/finkinfo/ethereal-ssl-0.9.3-1.info
...... entire 10.1 tree deleted .....

(This was not an upgrade installation, btw -- this was a fresh install on 10.2).

If I rm -rf /sw/fink/10.1, the problem goes away entirely, it seems.

Odd.

b.bum



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel


Reply via email to