> After digging in /sw/etc/apt/sources.list I noticed that I have to call
> "fink scanpackages" first! That it is not covered on the web site (or I did
> not find it) and it is not mentioned in the fink man page. hmm.
. . .
> Can anybody explain this "scanpackages" behaviour? Who is scanning what for
> who and what is being created?
Since your question solved a problem I had been working on for a couple
of hours, I will tell you what I know:
apt-get retrieves a file called Packages (usually Packages.gz) from the
repository of .deb files to build its list of dependencies. The Debian
tool to do this is dpkg-scanpackages, which uses an override file to
solve a slightly more complicated problem than fink has about which
packages are required, important or optional. All the required fink
packages are installed as part of the bootstrap process (those files
are in dists/local/bootstrap). So "fink scanpackages" just creates an
override file which mostly marks everything as optional and produces
the appropriate Packages.gz files.
I used this to propagate a fink source installation to a second
computer across my network. I was going down the path of trying to
generate an override file when your message arrived.
Thanks for your question!
-- John Montague
-- [EMAIL PROTECTED]
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
