On May 13, 2004, at 2:20 PM, Robert T Wyatt wrote:
Thanks Alexander! How's this summary:
===
(logged in as root)
fink scanpackages (makes packages built locally from source available to apt)
fink index (if asked to or when activating new Trees)
sudo apt-get update (tells apt what binaries are available)
sudo apt-get dist-upgrade (gets available binaries*)
fink index (just to be safe)
fink selfupdate (checks for/installs new fink version, updates source list)
fink update-all (gets/compiles source for files not available as binaries)
fink scanpackages (tells fink what dpkg did)
* available binaries will always be older than the source files, in both the stable and unstable trees, so it may not help much after initial installation of a package, but it won't hurt
===
At 1:52 PM -0400 5/13/04, Alexander K. Hansen wrote:On May 13, 2004, at 1:08 PM, Robert T Wyatt wrote:
I'm trying to give myself a set procedure to safely and intelligently update my packages. It's designed to be a list of things that never hurt, but some steps may not always be necessary. I'd like to know if there are steps that are never necessary in the order given, or if there is a better order to do them in, or missing steps, etc.
Here's what I've got with comments about what my impression is about why I'm doing it. Please add comments or steps that you think are appropriate:
(logged in as root)
fink scanpackages (refreshes fink's list of available files)
What this actually does is let apt know about packages that you've built from source on your local machine, so that it can treat them as available binaries, too.
fink index (rebuild the package cache)
Generally, you only need to run "fink index" if told to specifically, or if you activate a new Tree, e.g. unstable/main.
sudo apt-get update (tell apt-get what fink wants)
More precisely, update the list of packages that are available in binary form.
sudo apt-get dist-upgrade (get available binaries to save compile time)
fink scanpackages (tells fink what apt-get did)
This "fink scanpackages" is unnecessary, since you haven't built anything from source.
fink index (rebuild the package cache) fink selfupdate (checks for/installs new fink version)
And if you have CVS or rsync updating activated, rather than just updating to the next point release, this also updates the source distribution package list.
fink update-all (get updated files not available via apt-get)
fink scanpackages goes here.
I'm certain that I don't know exactly what I'm doing here, so any help is appreciated.
Thanks for your thoughts,
Robert
Also, as a general note, the source operations are going to update your packages long before any changes get made in the binary distribution. If you're using source, then the binary update stuff most likely won't do much.
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Fink-beginners mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-beginners
