Re: [darcs-users] Darcs equivalent of force-pushing and branching
On Fri, Sep 10, 2021 at 08:19:29PM +0900, Stephen J. Turnbull wrote: > James Cook writes: > > > For short-lived branches, I just use one clone per branch. I think this > > should work well for long-lived branches too, but I haven't tried. > > What's nice about the git storage model is that you can have a > "warehouse" repository with dozens of more or less active branches in > it, and two or three workspaces (which can even share the commit and > content storage of the warehouse, and the warehouse may not even have > a workspace). I've never wanted more than 3 workspaces, but when > doing release management stuff I've sometimes had as many as 10 active > branches I'm worried about in one session. > > git's storage model makes these workflows fast. Also, in the release > manager workflow, I often didn't need file content as such, I needed > diffs and merges, and the storage model makes it possible to diff and > merge across branches without a checkout (of course for merges the > target branch was always checked out, but in theory it didn't need to > be!) I've used git with multiple working directories, and it is nice. darcs uses hard links to save space, so having multiple clones should be relatively cheap. I only make light use of branches / work dirs / extra clones, but so far I have no complaints about using Darcs and just having one clone per workdir or branch. I don't know a nice command for diffing "branches" if the branches are Darcs repos, though. I guess I would use "diff -r" and filter out anything under _darcs. > All of this is obviously quite possible with Darcs. The problem is > getting the "accounting" right when separating the management of > *sets* of patches from the management of *histories*. IIRC, in Darcs > the history is in the patches, which means a bit of tedious surgery on > data structures needs to be done. I'm not sure what you mean by "histories" as distinct from "sets of patches". Shouldn't a branch just be a set of patches? -- James ___ darcs-users mailing list darcs-users@osuosl.org https://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Cannot create an account at bug.darcs.net
On Mon, 13 Sep 2021 13:14:12 +0200 Ben Franksen wrote: > (BTW we should really add TLS/SSL to the website and tracker.) FWIW, I find letsencrypt.org and certbot useful. Regards, Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein ___ darcs-users mailing list darcs-users@osuosl.org https://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Cannot create an account at bug.darcs.net
Hi Ganesh I guess this is a problem related to the roundup migration. If you could take a look at that? I tried twice to create an account with this email, but submitting the form fails with: Form is corrupted, missing: opaqueregister. (BTW we should really add TLS/SSL to the website and tracker.) Cheers Ben -- I would rather have questions that cannot be answered, than answers that cannot be questioned. -- Richard Feynman ___ darcs-users mailing list darcs-users@osuosl.org https://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Installing from source as a newcomer
Am 11.09.21 um 17:47 schrieb Alexis Praga: I wanted to build darcs from source and I have a few remarks: 1) The documentation says `cabal install darcs` but it's `cabal install exe:darcs` instead It may be necessary to be more specific when you invoke `cabal install` from inside a project's source tree. Otherwise a `cabal install darcs` should work. 2) The default cabal files fail to compile with cabal: filepath wildcard 'release/distributed-version' does not match any files. I had to edit the "release-data" section : -- release data - release/distributed-version - release/distributed-context + release/gen-version-info.hs A patch with my changes have been submitted to patc...@darcs.net. Of course, if I missed something, please tell me ! TL;DR: To `cabal install` from inside the darcs source tree you first need to manually execute a `runghc ./release/gen-version-info.hs`. Long story: In order to generate the (detailed) version info we have to be inside the darcs repo; but `cabal install` from inside a source tree first creates a source dist tar ball and then unpacks, builds and installs that. If we added the gen-version-info.hs to the sdist then it would be invoked during the build but since it is not inside a darcs repo, the version info would be incomplete. In earlier cabal versions one could add hooks to the sdist command but that feature was removed (in cabal-2.4, IIRC) for reasons that are not perfectly clear to me. The recommended solution by the cabal developers is to create VCS-dependent data (or modules) before calling `cabal sdist` when preparing a release, which is what we did. But of course this does not work when doing `cabal install` from inside the source tree, unless you manually generate the version info first, whereas `cabal build` works just fine because it builds directly inside the source tree. We should perhaps add a note in the README to make this clearer for new developers? 3) What's the difference betwen darcs.net and darcs.net/screened ? It's the same repo. Cheers Ben -- I would rather have questions that cannot be answered, than answers that cannot be questioned. -- Richard Feynman ___ darcs-users mailing list darcs-users@osuosl.org https://lists.osuosl.org/mailman/listinfo/darcs-users
