| 6 Oct 2021 |
 josephwright | In reply to @hmenke:matrix.org
I don't know for sure whether PGF does generate very long specials. There's the whole protocolling business | 10:31:14 |
| josephwright | In reply to @hmenke:matrix.org
There is actually a related thing that I wanted to discuss with the L3 team at some point (probably at a future TUG/Dante/etc meeting): More and more expl3 constructs are infiltrating the LaTeX kernel which is a good thing, since they bring new robust features, but the big downside is that \tracingall becomes more and more useless because expl3 produces lots of log spam. For most users this is a non-issue but developers will have a hard time tracking down bugs. We don't have to (and probably shouldn't) discuss this now; just something to keep in mind. I'll raise with the team and see how we want to approach it: one reason I pushed Frank to get a Zoom license is it does offer the possibility of running some kind of forum | 10:32:03 |
| josephwright | As in a live one | 10:32:13 |
 hmenke | josephwright: Matrix also supports conference calls. You could click the video call button in Element and it should start a Jitsi meeting. (Not good right now, this machine doesn't have a webcam/microphone 😄) | 10:37:02 |
| hmenke | If you want a channel for the L3 team I can create one. | 10:37:22 |
| hmenke | * If you want a room for the L3 team I can create one. | 10:37:34 |
| hmenke | The room can also be set to "by invitation only" | 10:37:58 |
| josephwright | In reply to @hmenke:matrix.org
If you want a room for the L3 team I can create one. At the moment I think we are OK :) | 10:38:00 |
| josephwright | hmenke: I see you have a build.lua file - is that 'live' and if so what functionality do I need to preserve? I have a feeling the heavy amount of coding reflects the fact that l3build was not as flexible in the past as it is now | 11:21:24 |
| josephwright | hmenke: My plan would be to start with a clean build.lua, add in the testing then add in the current functions too using the same structures | 11:21:59 |
| hmenke | josephwright: build.lua doesn't use l3build at all. | 11:22:00 |
| josephwright | hmenke: Ah, so it's just the name - right | 11:22:16 |
| hmenke | It's more or less a translation of the old Makefiles into a more or less cross-platform Lua script. | 11:22:44 |
| josephwright | Right, got it | 11:22:54 |
| josephwright | So if I rename at the moment in a PR, then build up the same outcomes? | 11:23:15 |
| hmenke | Feel free to completely break it in a PR. Just the main functionality has to be preserved, i.e. building the manual with all supported engines, creating a TDS archive and the CTAN flatdir archive. | 11:24:41 |
| josephwright | In reply to @hmenke:matrix.org
Feel free to completely break it in a PR. Just the main functionality has to be preserved, i.e. building the manual with all supported engines, creating a TDS archive and the CTAN flatdir archive. The only slightly challenging thing is the manual, I think: I might need some custom functions, but that's a lot easier than it used to be | 11:25:16 |
| josephwright | In reply to @hmenke:matrix.org
Feel free to completely break it in a PR. Just the main functionality has to be preserved, i.e. building the manual with all supported engines, creating a TDS archive and the CTAN flatdir archive. CTAN releases are a core part of l3build :) | 11:25:27 |
| josephwright | hmenke: I've made a start - https://github.com/josephwright/pgf/tree/l3build-tests | 12:25:23 |
| josephwright | hmenke: I'll need a little while to look at all the detail - the key first step was to be sure I could do the installation | 12:29:48 |
| josephwright | hmenke: I'll probably talk with Marcel about a setting that would preserve the source structure entirely here: the rather awkward file map is needed as we don't (normally) do that | 12:30:24 |
| hmenke | You can easily generate the filemap from git ls-files | grep '^tex/' | 12:30:58 |
| hmenke | This is how I generated the list of files to install before: https://github.com/pgf-tikz/pgf/blob/a0d9cadad21da7c525570d3a88124708588c46fb/build.lua#L225-L270 | 12:32:15 |
| josephwright | In reply to @hmenke:matrix.org
You can easily generate the filemap from git ls-files | grep '^tex/' I did find . -type f, but the idea's the same :) | 12:37:45 |
| josephwright | In reply to @hmenke:matrix.org
This is how I generated the list of files to install before: https://github.com/pgf-tikz/pgf/blob/a0d9cadad21da7c525570d3a88124708588c46fb/build.lua#L225-L270 I'll perhaps think about that in a little while - first I want the typesetting working, and that seems ... odd | 12:38:29 |
| hmenke | In reply to @josephwright:matrix.org
I did find . -type f, but the idea's the same :) Okay, but git ls-files will only list files that are actually tracked by git. | 12:38:33 |
| josephwright | hmenke: Nearly the end of my lunch break so will come back to it later :) | 12:39:16 |
| hmenke | josephwright: Thanks for sacrificing your lunch break for this. | 12:39:48 |
| josephwright | In reply to @hmenke:matrix.org
josephwright: Thanks for sacrificing your lunch break for this. It's quite fun | 12:39:57 |
| josephwright | In reply to @hmenke:matrix.org
Okay, but git ls-files will only list files that are actually tracked by git. I went for hard-coding in the first instance as that's a good place to start, then we can refine once I have everything else working - in particular a demo test and typesetting the docs | 12:42:41 |
