glycerine / vj Goto Github PK

---------- Forwarded message ----------
From: Eric Sink <[email protected]>
Date: Fri, May 15, 2015 at 8:26 AM
Subject: Re: veracity
To: "Jason E. Aten" <[email protected]>

The reproduction on that bug *should* be simple.  Create a repo with lots of files, perhaps 500 or so.  Delete perhaps 100 of them.  A delete of a single directory with 100 files in it should suffice.  After that, the working directory is in a broken state.  A simple "vv status" should print an error message.  Lemme know if this recipe doesn't show you the bug.  The working directory state is stored in a sqlite database.  Somewhere in that code is a problem.

I will see about getting you that todo list.

--
E


On Fri, May 15, 2015 at 10:00 AM, Jason E. Aten <[email protected]> wrote:

    Hi Eric,

    Thanks for the details. Sorry the business around veracity didn't work out.

    If you would be so kind as to send over the details of how to reproduce that one bug 
    with the bunch of deletes from the working folder all at once, I would like to try my hand
    at making a fix; to let me test the waters.

    That is, I'll try to fix it as a means of evaluating how easily I could make headway in adding to/working with veracity.

    I was able to build the 2.5 release sources on centos 6.6/amd64 in debug mode without much hassle, so that is encouraging. Just had to install the spidermonkey 1.8.5 release before the cmake files would configure properly, and that much wasn't described in the doc/install instructions.

    If the todo list is public, could you point me at it--otherwise would you mind sending me a copy of full details?

    I really like the idea in veracity of having a database style record/field interface versioned along with your source code and you bug databases. I think that is brilliant.

    Thank you so much!

    Jason

    On Fri, May 15, 2015 at 4:48 AM, Eric Sink <[email protected]> wrote:


        Hi Jason,

        Unfortunately, development on Veracity stopped.  We were not successful in building a business around it.

        The latest release is in pretty good shape.  We use it everyday.  There is one annoying bug which happens when you do a bunch of deletes from the working folder all at once.  I haven't looked at the todo list in a while, and I'm sure there are things we planned to do.  But in general, we've got a fairly complete set of operations and it works well.

        E


        On Friday, May 15, 2015, Jason E. Aten <[email protected]> wrote:

            Hi Eric,

            I happened to pickup your Version Control by Example book the other day, and I was just checking out veracity's website.

            It looks like a bunch of the links on the veracity website are dangling, especially things like the .deb files and the FAQ. Did development on veracity go somewhere else; or did it just stop?  What is the story there, I'd be very curious.

            I might be interested in working on veracity a little in my spare time. Could you indicate what kind of state the 2.5 release represents?  In other words, what is there, what is missing, what is working well, what is not... that kind of description would be helpful.

            Thank you!

            Best regards,
            Jason

            --
            Jason E. Aten, Ph.D.
            [email protected]

---------- Forwarded message ----------
From: Eric Sink <[email protected]>
Date: Fri, May 15, 2015 at 8:27 AM
Subject: Re: veracity
To: "Jason E. Aten" <[email protected]>



Actually, we never did do the submodules feature.  :-(

--
E


On Fri, May 15, 2015 at 10:09 AM, Jason E. Aten <[email protected]> wrote:

    Ah--one other quick questions, if I may:

    I noticed there was a nice summary comparison of veracity and other DVCS here; http://demin.ws/blog/english/2012/05/17/veracity/, which suggests that submodules were coming soon in 2012.

    With respect to submodules, where do things stand at the 2.5 veracity release? By submodules I assume that we are talking about the ability to point from one veractiy repo to another; or to have nested repos with separate access controls.

    Thanks!

    Jason