Altering the Trees: line just gives you access to unstable versions. You can still update from CVS without doing this--but you'll only see updates to the stable tree.
Is there some reason you aren't just using 'fink selfupdate' or 'fink selfupdate-cvs' to do the update, especially since the message the system gives you says that you are set up for it? -- Alexander K. Hansen Associate Research Scientist, Columbia University Levitated Dipole Experiment MIT Plasma Science and Fusion Center, 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 Phone: 617-252-1818 Fax: 208-988-4057 On Tue, 16 Apr 2002, Zorro wrote: > What I did: > Altered finkconf to: Trees: local/main stable/main unstable/main stable/crypto >local/bootstrap > Was that necessary? I read to do that somewhere albeit not on the cvs access web >page. > Then, according to cvs access page, I ran the commands in order. So far so good. > Now when I run the ./inject.pl for pkg manager it will update fink. > For today it's fink (0.9.11.cvs-20020416.1738) > But when I run: > cd tempdir/packages > cvs -z3 update -d > ./inject.pl > the return is: > The directory '/sw' contains a Fink installation that was set up to get > package descriptions directly from CVS. This script will not update this > installation. Run 'cvs update -d -P' in the directory '/sw/fink' instead. > I do, and it works, but it seems I am missing something. > Why the extra step? > And where does fink selfupdate-cvs come in? > Thanks > Zorro > > > _______________________________________________ > Fink-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/fink-users > _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
