-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove outdated questions #15
Conversation
These changes haven't propagated to the live site. Does anyone know why? |
My changes did not propagate either, yet. @emilypi says the bytes need to be moved to the actual www site on a floppy drive and then it will show fine. Promises to send a boy soon. |
There's something particularly strange about this case because the changes from other commits that were merged later have already propagated to the live site. I wonder if there's something special about the |
Yes - this site, for whatever the historical reason, is not automatically deployed. I'm not sure why other commits are live. |
@tomjaguarpaw: the floppy with the FAQ seems to have reached the site as well. Could you verify? |
I'm not sure what you mean. I'm looking at https://www.haskell.org/cabal/FAQ.html and I still see "Hidden packages (a)" and "Hidden packages (b)", for example. There should only be one "Hidden packages" section after this PR. |
@tomjaguarpaw: that's not what I see. Try clearing browser cache? |
That's very interesting. Shift-reload successfully fetched me the new page and I see that this PR is indeed reflected in it! Was this PR already there yesterday and my stale cache was just making me think otherwise? Anyway, all good as far as this PR is concerned. Thank you to whoever sent the floppy! |
You're welcome :) |
All of the FAQ questions seem to be pretty outdated. This PR removes the ones that are extremely outdated, specifically
💀 Dependencies conflict
Refers to behaviour from old cabal that doesn't really occur with modern cabal (say from 3.0 onwards). It mentions GHC 6.10!
💀 Hidden packages (b)
It's about a library split that happened in GHC 6.8. It is no longer relevant.
💀 runghc Setup complains of missing packages
This seems to be referring to a rather old way of installing packages. I really doubt it is a frequently asked question.
💀 Parsec 2 vs 3
Parsec 3 was released in 2008. Highly doubtful that this is an asked question, let alone frequently.
💀 Cabal goes into an infinite loop / runs out of memory
"This happens when you use cabal-install version 0.5.x with ghc-6.10". cabal-install version 0.5 is from 2008.
💀 Internal error: invalid install plan
Suggests upgrading to "cabal-install >= 0.10". Was new in 2011, now severely out of date.
I ran
make
to generateFAQ.html
fromFAQ.md
. I hope that was the right thing to do.