Camelia, the Perl 6 bug

IRC log for #darcs, 2006-04-29

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
04:17 Jerub attempts to spend some time fixing his tailor/darcs problem.
05:27 araujo Hello.
05:27 lispy hi
08:11 C-Keen hi
12:41 weary when configuring darcs, if it tells me "Could not find module `Prelude'", i assume something is wrong with my ghc installation. any idea what?
12:42 Jerub weary: use a binary.
12:42 weary gentoo :)
12:42 Jerub weary: use a binary.
12:43 Jerub weary: the problem is actually quite simple. GHC is a compiler. You've got a 'bootstrap' compiler for GHC. In order to compile darcs you're going to need to use the bootstrap GHC to compile GHC.
12:44 Jerub weary: on my powermac, that takes a couple hours.
12:44 Jerub then, compiling darcs is a couple minutes.
12:44 Jerub or! you can just use a binary.
12:44 weary on amd x2 that should be less, and i have an old version of darcs, i can wait
12:45 Jerub http://darcs.net/DarcsWiki/Cat[…]e3cb834faceb123cf
12:45 Jerub also, this is probably the easiest way of getting the latest: http://darcs.net/DarcsWiki/Cat[…]009e0570d2143f152
12:46 weary if possible, i'll stick with portage, i'll emerge ghc
12:47 weary ghc-bin should be enough, but apparently it is missing something
12:47 Jerub I think the wiki lies
12:47 Jerub we had someone here a few weeks ago with exactly this problem.
12:48 weary must be
12:48 Jerub update it to reflect your experiences.
12:48 weary ok. i'll just wait 'n see if using the ghc-package solves anything
13:06 weary ok. that was easy. re-emerge of ghc-bin solved it. wiki updated
13:07 weary i also updated the emerge-instructions, i think it was missing a ~x86 in the echo line
14:56 xerox tries to compile darcs with experimental ghc-6.5 for i386-darwin-apple ... brrrr! :-)
14:59 xerox Linking darcs ...
14:59 xerox _ControlziMonadziError_zdf22_closure
14:59 xerox _ControlziMonadziError_ZCDError_static_info
14:59 xerox _ControlziMonadziReader_polyzufail_closure
14:59 xerox _ControlziMonadziReader_polyzufail_info
14:59 xerox collect2: ld returned 1 exit status
14:59 xerox sob.
15:20 xerox Woohoo, it built!
15:24 weary *cheer*
15:33 xerox What is wxDarcs?
15:34 xerox I mean the one in the darcs tarball... it doesn't seem to open a wx GUI, but darcs itself.
15:35 Igloo darcs has a WX GUI for some operations...don't know if that's what you're refering to
15:35 xerox Seems not.  "make wxDarcs.app"
15:35 xerox I'm just trying to understand if there is a clean way to install darcs now, in fact.
15:36 xerox Unfortunately darwinports doesn't recognize my ghc (which I built in-place.)
15:36 Igloo I think you need a --gui argument if you actually want to use the GUI
15:36 xerox $ ./wxDarcs --gui
15:36 xerox darcs failed:  Invalid command '--gui'!
15:36 Igloo make install should work, but obviously won't interact with any packaging system you may have
15:36 xerox Right.
15:36 xerox Does it provide a make uninstall perchance?
15:36 Igloo The argument is probably to the command. I've never tried it myself, though
15:36 Igloo No idea
15:38 xerox MD5 (darcs) = 8ed8295acc13f89ef15275998ab14f9f
15:38 xerox MD5 (wxDarcs) = 8ed8295acc13f89ef15275998ab14f9f
17:21 lispy 1) fix the theoretical problems with patch theory and implement them (you have to write code to get paid by google).  2) cleanup the performance 3) finish the gui 4) improve tortoise darcs 5) tackle random bugs in the bug tracker 6) add darcs support to various IDEs 7) factor darcs into a library
17:21 lispy those are just the ones that come immediately to mind
17:22 Igloo 1 is a bad idea if you want to be confident of finishing this summer
17:22 lispy hehe
17:22 lispy it's still important though
17:23 lispy Igloo: can you think of any fun SoC darcs projects that i missed?
17:23 Igloo Yes, but I thought you were listing things that would make good SoC projects
17:23 lispy my projects probably don't sound very fun
17:23 Igloo 5 ought to cover all the actual darcs ones. If not, someone should file some bugs  :-)
17:23 lispy heh
17:40 tschwinge knows a darcs SoC project: make it usable non-interactively.
17:41 lispy tschwinge: yeah, that might actually be more useful than my #7
17:41 lispy but i'm partial to the 'libdarcs' idea :)
17:42 tschwinge #7?
17:42 Igloo The "7) factor darcs into a library" in the above list
17:43 Igloo # means "number" in some contexts
17:44 tschwinge Right, no I understand.
17:44 tschwinge Gah.
17:44 tschwinge s/no/now
17:51 xerox Ooh, those are nice!
18:25 piggybox how to use darcs to sychronize two project folders on two computers without network?
18:31 ohub I think you could do that with darcs send --output=FILE in first end and darcs apply FILE on another.
18:32 ohub or maybe you could have a repository in USB stick or something and then do pulls and pushes to it.
18:36 piggybox Hi ohub, I've got some clues from the wiki. Since there's not web server, I have syndicate the context(changes log) by myself between two projects in order to use send/apply
18:37 piggybox I will try the idea of mutual folder in a USB sticker. Thanks.
18:39 ohub You can have the "main" repository in your USB stick and then use it like any other darcs repository.
19:04 piggybox Yes, I've tried. It's very easy. Darcs's wonderful.
19:06 piggybox I didn't knew from the document that I can use normal file directory in addition to urls.
19:07 piggybox I was looking for send/apply solution, but it requires taking care of different contexts, which is quite bothersome.
19:09 ohub yeah
19:10 forcer It seems darcs dist only has --posthook - isn't there a "prehook" so I can adjust the contents of the tarball?
19:21 lispy forcer: no prehooks, but yeah, darcs could benefit from them
19:24 forcer Yeah, couldn't it...

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary