From psihopat.v.metroto at gmail.com Mon Feb 25 19:52:47 2019 From: psihopat.v.metroto at gmail.com (Viktor Grigorov) Date: Mon, 25 Feb 2019 19:52:47 -0000 Subject: [darcs-users] darcs on winos Message-ID: Hello, Resending initial email as per suggestion of Simon.: "Having gotten increasingly tired of git I looked into alternatives, mercurial's 2/3 installers failed, and command line tool was also somehow deficient, and oh, how it half-heartedly it was written for the windows os. Knew of darcs, decided to give it a try. Spent a good 3 hours trying to get the damn shit installed or working. The closest I think I got was the dl'd binary, which brings up a mere help file in the console and terminates. No instructions, nada. Getting the haskell platform, getting cabal, updating (with new-update, rather than update as the documentation clearly hasn't been updated in some time), and the "cabal new-install darcs -f-curl" begins a 15'-long crawl thru molasses- 2 sh.exe's, 3 cabal.exe' and 2 ghc.exe's, all totaling >2.5Gb RAM and 70% CPU usage- dowloading and building as if every package in existence. . . Afterwards, "darcs" is still not recognized in cmd, mingw/msys's bash. A system seach of "darcs" retrieves abs.nothing. All the docs insist on typing "darcs ...", as if it doesn't matter where you type it. Please, get somebody to fix the documentation, or just scrape the windows sections until you have something that works." I'll add to that, thatI tried mercurial, as described above; tried bazaar- doesn't recognize folder and exits; tried gitlabs, the 'housekeeping' thing there that's supposed to delete unreferenced files, however those are defined, didn't work, deleting the files from the initial commit didn't let me merge, they have no tutorials or instructions on this very, very simple task; tried darcs- literally 3 hours of trials running into the morning, into giving up because fuckall for useful documentation or instructions on getting it to work. Maybe there's >1 things I'm doing fundamentally wrong, but I believe that a should should have the the ability to brick his repo, system, computer etc., instead of sb holding his hand and saying 'oh, no-no-no, you don't wanna do that sweaty, you have to either work by some arbitrary, inconveniently contrived 'standards', comprised of language ranging from the usual of semi-descriptive up to and not excluding whimsical and downright unhelpful- `squash, smash, bash, crash, rebase, remerge, submerge, pumpkin-nut-tickle` etc. This is unacceptably bad, even if I am wronging the 'wrong' way, even if I'm a sub-200-IQ brainlet. Whatever happened to simplicity, and documentation? Why offer the product for windows, if it's so half-hearted? Sincerely, vlg -------------- next part -------------- An HTML attachment was scrubbed... URL: