--- Log opened Wed Aug 16 00:00:30 2023
00:17 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
00:37 -!- zack__ [~zack@26.sub-174-215-179.myvzw.com] has joined #secp256k1
00:56 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
01:22 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
01:40 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
02:12 < real_or_random> thinking about my comments that led to  https://github.com/bitcoin-core/secp256k1/pull/1401 ...
02:14 < real_or_random> I think, the docker images were initially created to speed up CI. And they still serve this purpose well, in particular because we build our own GCC. 
02:16 < real_or_random> The second purpose is that they make development easier. Again, this is emphasized with the snapshot GCC and clang, and with other exotic builds, e.g., cross-compilation. If we run into issues there, it's usually easier to build the docker image locally than to install some snapshot clang on your own machine (in particular if you don't use debian)
02:21 < real_or_random> The question is how important the second purpose is in the case of MSVC. None of us uses Windows. Installing MSVC on Linux is not trivial but the scripts in https://github.com/mstorsjo/msvc-wine do a good job.
02:22 < real_or_random> Oh they actually have a Dockerfile... https://github.com/mstorsjo/msvc-wine/blob/master/Dockerfile  
02:22 -!- zack__ [~zack@26.sub-174-215-179.myvzw.com] has quit [Quit: a]
02:24 < real_or_random> Okay, in that case, I really think  we can split these purposes. If we take the approach in 1401, we won't need to install MSVC in our Docker image. If it turns out that people need a Dockerized MSVC, they can build https://github.com/mstorsjo/msvc-wine/blob/master/Dockerfile
02:40 < real_or_random> hebasto: I can't parse this output https://github.com/bitcoin-core/secp256k1/pull/1401#discussion_r1295641317
02:41 < hebasto> real_or_random: it is output of the `dir` command in powershell from within a GH Windows runner that shows multiple versions of MSVC tools being installed
02:42 < hebasto> invoking `cl.exe` using `*` won't work
02:52 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
02:58 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
04:05 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
04:14 -!- tromp [~textual@92.110.219.57] has joined #secp256k1
05:13 -!- tromp [~textual@92.110.219.57] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
05:27 -!- jonatack2 [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
05:27 -!- jonatack2 [~jonatack@user/jonatack] has joined #secp256k1
07:04 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
07:18 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
07:22 < achow101> would it make sense to give the libsecp maintainers admin over that repo? (do they want it?)
07:22 < achow101> would make the actions stuff a bit easier as they can update those settings as needed instead of having to ping one of the org owners
07:23 < sipa> i think it would make sense
07:24 < fanquake> are the settings repo specific, or is enabling things global across the org?
07:24 < achow101> repo specific
07:27 < achow101> there's a couple of org-wide rules but those shouldn't be changed per-repo, e.g. whether github can write to the repo
07:30 < fanquake> Yea, no-one should need to turn any of that type of stuff on in any case
08:19 < real_or_random> I agree that it makes sense, and it's ok for me to take the permissions
08:42 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
08:49 -!- preimage [~halosghos@user/halosghost] has quit [Read error: Connection reset by peer]
08:50 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
09:17 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
09:47 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
10:09 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
10:16 -!- jonatack2 [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8]
10:25 -!- jonatack [~jonatack@user/jonatack] has joined #secp256k1
11:20 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
11:21 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
13:34 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
14:22 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.0.3]
22:20 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
23:08 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
23:10 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
23:22 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
--- Log closed Thu Aug 17 00:00:31 2023