From gdt at lexort.com Wed Oct 21 07:29:01 2020 From: gdt at lexort.com (Greg Troxel) Date: Wed, 21 Oct 2020 07:29:01 -0400 Subject: [Unison-hackers] notice of intent to use this list! Message-ID: An embedded and charset-unspecified text was scrubbed... Name: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: not available URL: From mikebohde at gmail.com Wed Oct 21 12:07:20 2020 From: mikebohde at gmail.com (Mike Bohde) Date: Wed, 21 Oct 2020 12:07:20 -0400 Subject: [Unison-hackers] 2.51.3 Release feedback Message-ID: One of the common threads I've seen in this list and the users list was the speed increase / decrease by the newer versions. In my use case ( Fedora 32 ) the new release is much faster to scan for changes and about the same to sync. I updated to the v2.51.3+ocaml-4.11.1 binary from the 2.48 version in the fedora repository. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gdt at lexort.com Thu Oct 22 08:22:03 2020 From: gdt at lexort.com (Greg Troxel) Date: Thu, 22 Oct 2020 08:22:03 -0400 Subject: [Unison-hackers] installation instructions for github binaries Message-ID: Someone brought to my attention that there aren't installation instructions for the CI-generated binaries. I have only looked at the Linux one to try to run it on NetBSD (which can in general run Linxu binaries), and it seemed straightforward. But macOS and Windows are probably harder. If anyone would like to add instructions, please edit the wiki: https://github.com/bcpierce00/unison/wiki/CI-Binary-instructions I put this on a separate page because it's likely going to end up too long to avoid interfering with the flow of the high-level page. From gdt at lexort.com Thu Oct 22 08:53:34 2020 From: gdt at lexort.com (Greg Troxel) Date: Thu, 22 Oct 2020 08:53:34 -0400 Subject: [Unison-hackers] will start merging perhaps 18Z Message-ID: I will be trying to reduce the numbe of open PRs, tending to look at those that are simple and obviously right. After 18Z today, I will start hitting merge next time I have a chunk of time, on the three PRs in "approved" status. Speak up if you think that's not the right thing to do. I think these two are also ready, but would appreciate someone else looking at them as I am not an ocaml expert or very familiar with the unison codebase: https://github.com/bcpierce00/unison/pull/402/commits https://github.com/bcpierce00/unison/pull/390/commits (This message is not meant to be a comment on any others.) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: not available URL: From gdt at lexort.com Thu Oct 22 15:29:37 2020 From: gdt at lexort.com (Greg Troxel) Date: Thu, 22 Oct 2020 15:29:37 -0400 Subject: [Unison-hackers] New list of PRs I would like review help on In-Reply-To: (Greg Troxel's message of "Thu, 22 Oct 2020 08:53:34 -0400") References: Message-ID: I have merged 4 PRs. Here is my new list of PRs that I am ok with but would like someone else who understands to comment on. Basically I'm going to merge them Sunday if there are no objections, some earlier as marked as I'm more confident. * https://github.com/bcpierce00/unison/pull/402 Skip user actions after reconciliation in batch mode * https://github.com/bcpierce00/unison/pull/373 copyonconflict: improve behavior with deleted files * https://github.com/bcpierce00/unison/pull/362 change default diff ordering * https://github.com/bcpierce00/unison/pull/360 color text by default, via hardwired ANSI (not termcap) That leaves 11 PRs to go - based on other PRs - PRs needing rebasing - PRs marked wip - PRs marked feedback - PRs that I have not evaluated yet (ACL) - old PRs (that may well be entirely valid) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: not available URL: From gdt at lexort.com Sun Oct 25 09:52:17 2020 From: gdt at lexort.com (Greg Troxel) Date: Sun, 25 Oct 2020 09:52:17 -0400 Subject: [Unison-hackers] how far do we want to go in packaging? Message-ID: We had a question about how to install the CI-generated mac binaries, and Roy suggested creating .app bundles. Thoughts arising: - The main point of CI is CI. - We could go down the path of producing native packages for N packaging systems, where N tends to get very large. In the limit this is crazy and impossible. - Many packaging systems tend to be behind, and the ocaml version problem means that one needs to use a portable packaging system with consitent builds across systems, but people dont'. - We do seem to have a lot of users that can't build from source or deal with this. - It seems someplace in the middle is warranted; I really don't want to go very far down this path. - That could be the missing instructions at https://github.com/bcpierce00/unison/wiki/CI-Binary-instructions - That could be making the CI binaries more package-y. - Part of the issue is the protocol break problems and fixing that is IMHO the most important thing to do. (in progress, I know) This is something I'm not personally interested in, as I use pkgsrc for this (and maintain the unison entry in pkgsrc). I'm happy to glance at PRs, issue pleas for others to review, and hit merge if I think there's consensus about the approach and that there's been adequate review. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: not available URL: