Here's the material that I said I'd add to the FAQ (I don't have commit access):
[ldx3:~/web/xml/faq] hansen% cvs diff -u faq.xml Index: faq.xml =================================================================== RCS file: /cvsroot/fink/web/xml/faq/faq.xml,v retrieving revision 1.46 diff -u -r1.46 faq.xml --- faq.xml 20 Oct 2002 20:23:19 -0000 1.46 +++ faq.xml 4 Nov 2002 15:26:35 -0000 @@ -482,6 +482,16 @@ software before using Fink. </p></answer></faqentry> +<faqentry name="not-found"><question><p>I'm trying to install a package, but fi nk can't download it. The download site shows a later version number of the pac kage than what fink has. What do I do?</p></question> +<answer> +<p>The package sources get moved around by the upstream sites when new versions are released.</p> +<p>The first thing you should do is let the package maintainer (available from "<code>fink describe <em>packagename</em></code>") know that the URL is broken; not all maintainers read the mailing lists all of the time.</p> +<p>To get a usable source, first try hunting around the remote site in other di rectories for the source that fink wants (e.g. in an "old" directory). Keep in mind, though, that some remote sites like to trash the old versions of their pac kages. If the official site doesn't have it, then try a web search--sometimes t here are unofficial sites that have the tarball you want. If that fails, then y ou might consider posting on the +<link +url="http://www.mail-archive.com/fink-users@;lists.sourceforge.net/">fink-users mailing list</link> to ask if anybody has the old source available to give you. Once you locate the proper source tarball, download it manually, and then move t he file into your fink source location (i.e. for a default fink install, "<code> sudo mv <em>package-source.tar.gz</em> /sw/src/</code>". Then use '<code>fink i nstall <em>packagename</em></code>' as normal.</p> +<p>If you can't get the source file, then you'll have to wait for the maintaine r to deal with the problem. They may either post a link to the old source, or u pdate the .info and .patch files to use the newer version. +</p></answer></faqentry> + </chapter> @@ -604,6 +614,16 @@ fink update gettext</codeblock> </answer></faqentry> +<faqentry name="libgtop"><question><p>libgtop fails with errors involving sed.< /p></question> +<answer> +<p>This can happen if your login script (e.g. <code>~/.cshrc</code>) does somet hing that writes to the terminal, e.g "<code>echo Hello</code>" or <code>xttitle </code>. To get rid of the problem, the easy solution is to comment out the off ending lines.</p> +<p>If you want to keep the echo, then you can do something like the following:< /p> +<codeblock> +if ( $?prompt) then +echo Hello +endif +</codeblock> +</answer></faqentry> </chapter> -- Alexander K. Hansen Associate Research Scientist, Columbia University visiting MIT Plasma Science and Fusion Center Levitated Dipole Experiment 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
