Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2017-05-02

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

All times shown according to UTC.

Time Nick Message
00:54 mizu_no_oto 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:26 mizu_no_oto joined #darcs
02:54 mizu_no_oto joined #darcs
03:32 mizu_no_oto joined #darcs
05:44 leg1 joined #darcs
06:06 Heffalump pointfree: catching up with Sunday - so you're thinking of storing bits of darcs repos in couchdb? Or just submitted patches?
06:39 masse joined #darcs
06:50 bf_ joined #darcs
08:23 alqatari joined #darcs
09:11 Weltraumschaf joined #darcs
09:46 aristid joined #darcs
10:59 alqatari joined #darcs
14:03 leg joined #darcs
14:36 leg joined #darcs
14:48 lambdabot joined #darcs
15:04 pointfree joined #darcs
15:08 * pointfree[m] sent a long message: pointfree[m]_2017-05-02_15:08:42.txt - https://matrix.org/_matrix/media/v1/download/matrix.org/LfWITjlpCEqEGANgoCMVxpZp
15:09 pointfree Heffalump: Right now the feed uses couchdb, but I think sm and myself want to move away from couchdb instead of depending on it even more. Right now we are using a different couchdb database for each feature and it makes it hard to integrate the data across them.
15:09 pointfree Now I'm thinking we could use Haskell Persistent https://github.com/yesodweb/persistent
15:09 pointfree Because Persistent is database agnostic, we could use sqlite or whatever for metadata, the redis backend for transient stuff, AND write a persistent backend for the darcs repo format.
15:09 pointfree This way we could integrate data from various sources without needless redundancy, and not have to store darcs repos in any funky way.
15:10 pointfree (I'm just trying out riot/matrix.org for irc and didn't know it would send my long message as a link)
15:11 sm pointfree: that was my thought as well, for anything that can't be better stored in the darcs repo
15:12 sm try sqlite and move to postgres if necessary
15:40 alqatari joined #darcs
15:48 Riastradh joined #darcs
16:02 pointfree Writing a thin Database.Persist.Darcs wrapper may be a fun way for me to get into actual darcs development. I don't know much about Persistent yet, but my hope is that Persistent will be a generic interface to heterogeneous data sources across different darcs repos, sqlite/postgres, and redis.
16:02 pointfree sm: Btw, a rather trivial patch related to SSL: https://hub.darcs.net/pointfree/darcsden-security/patch/403ede9c9988dccb811a49edab5b7bbb7c4a8d81  It could be deployed whenever you feel like it.
16:02 bf_ joined #darcs
18:08 sm I saw! thanks pointfree, will check it out
18:33 alqatari joined #darcs
18:47 Heffalump hmm, so you want to make a new repo backend? That sounds nice, but maybe a bit like hard work with the current darcs code
19:11 pointfree Heffalump: A Database.Persist wrapper for the existing darcs repo format. I don't currently know all that much about the internal Darcs code itself, only about DarcsDen and the _darcs/ format.
19:26 pointfree A lot of what a DVCS does is analogous to what a database does. https://www.kenneth-truyers.net/2016/10/13/git-nosql-database/
19:32 sm uh.. hmm
19:32 * sm was just talking about the extra metadata darcsden tracks in couchdb
19:35 pointfree hm?
20:40 Heffalump pointfree: oh, I see. That shouldn't be so hard. The internal API is mostly transactional, with some warts.
20:43 Heffalump and yes, I agree VCS and databases are quite similar in some ways, but with very different ergonomics and performance.
21:12 pointfree At the moment I think I'd only like to use darcs as the DBMS for information already stored in _darcs/
21:12 pointfree Heffalump: I suppose aggregating and sourcing news feed items from _darcs/ directly also influences usage of the darcs post-hook api.
21:12 pointfree With the post-hook api I as largely copying what was already in _darcs/ into couchdb.
21:12 pointfree We still need the post-hook api to close issues from patch summaries and possibly open issues from FIXME's and TODO's in source code comments.

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