Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2017-05-16

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:18 mizu_no_oto joined #darcs
00:29 Riastradh joined #darcs
01:48 ilbot3 joined #darcs
01:48 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.12.5 is out http://darcs.net/Releases/2.12
02:03 mizu_no_oto joined #darcs
05:52 ThomasLocke joined #darcs
05:52 ThomasLocke joined #darcs
06:10 vikraman joined #darcs
08:13 Weltraumschaf joined #darcs
11:03 Weltraumschaf joined #darcs
11:26 Weltraumschaf joined #darcs
11:56 Weltraumschaf joined #darcs
14:28 mizu_no_oto joined #darcs
14:34 hseg joined #darcs
14:37 hseg Hi. Considering moving to darcs from git. Couple of questions. A) How is the Windows support? B) How well are large (~100MB) binary files handled? C) Does darcs support tracking who has copies of a certain file (cf. git-annex)?
14:45 hseg joined #darcs
15:32 hseg joined #darcs
15:42 hseg Hello? Any answers to my questions? (for reference: Considering moving to darcs from git. Couple of questions. A) How is the Windows support? B) How well are large (~100MB) binary files handled? C) Does darcs support tracking who has copies of a certain file (cf. git-annex)?)
15:48 pointfree hseg: Doesn
15:49 pointfree t git-annex just store metadata.
15:49 pointfree *hit the enter key too soon
15:53 hseg git-annex does many things. Specifically what I'm thinking of is that it only commits a filename+hash to the repository, and maintains a hash-value store on its own. Moreover, this store can be distributed over multiple computers, with git-annex keeping track of who has copies, so that you can say "Forbid me from deleting anything from the store that doesn't have at least 2 remote copies"
16:00 pointfree hseg: Maybe darcs' patch/content-centric model could make for an interesting annex-like tool.
16:00 pointfree regarding windows support, I can't speak for it myself because I'm using linux, but darcs was designed to have first class Windows support from the start, more so than git (which was designed to support linux kernel development)
16:03 hseg joined #darcs
16:04 peb` joined #darcs
16:06 hseg pointfree: Sorry, missed your response. So windows support should be OK?
16:06 leg joined #darcs
16:08 hseg Searching regarding large files, I see some bugs have been reported.
16:08 hseg But that's not that big of a concern
16:09 pointfree hseg: Yes, it should be. There are people using darcs on windows on the darcs mailing lists. Looks like there is a recent Windows exe of darcs here http://darcs.net/Binaries
16:11 hseg OK, good.
16:12 hseg I see that cygwin support isn't that good, though.
16:15 hseg Similarly to the large-files thing, the lack of copy tracking is annoying, but not a concern.
16:15 pointfree hseg: darcs does support copy/move tracking.
16:15 hseg In fact, the two things that are attracting me most to darcs are the sane patch logic and the copy/move tracking.
16:16 hseg pointfree: I meant copy in the sense of "who has a copy of this" not in the sense of "a is a copy of b"
16:29 pointfree hseg: Perhaps the spontaneous branch workflow + darcs log <filename> could support a darcs-annex-like usage pattern. Darcs subcommands generally support aggregating patches like twitter aggregates tweets with hashtags. They also take file paths as arguments for filtering patches. http://darcs.net/Features#the-darcs-way-of-non-branching
16:29 pointfree You could include the location in the commit message with something like P#location (+ filter by filename) ...or you could make it more content-centric and do the hashtags and repos by topic.
16:31 hseg_ joined #darcs
16:36 Heffalump hseg: TBH, darcs handles large binary files very badly. It stores them as a (compressed) base64 encoding and every time you change a single byte, you get two copies of the entire file in a patch. That said, computers have got a lot faster over the last years and maybe in practice the overheads wouldn't matter to you.
16:37 hseg OK, but so infrequently mutating files on the <100MB scale should be OK?
16:39 Heffalump well, I'd try it for yourself to see
16:39 Heffalump but I think it wouldn't be a complete car crash
16:40 amgarchIn9 joined #darcs
16:42 hseg OK
16:50 hseg joined #darcs
17:12 tg joined #darcs
17:42 amgarchIn9 joined #darcs
18:00 siel joined #darcs
18:05 mizu_no_oto joined #darcs
18:25 amgarchIn9 joined #darcs
18:29 Riastradh joined #darcs
18:40 alqatari joined #darcs
18:49 stef204 joined #darcs
18:51 stef204 joined #darcs
18:56 peb` joined #darcs
21:05 mizu_no_oto joined #darcs
21:22 Weltraumschaf joined #darcs
22:57 leg joined #darcs
23:10 stef204 joined #darcs
23:37 stef204 joined #darcs
23:51 stef204 joined #darcs

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary