Make patching task

[roaldarbol]

Hi there!

I'm just beginning to try uploading a few packages to Typst-Forge, especially in an effort to identify obstacles to wider adoption - I think having this forge is a super initiative and would love to be able to rely on it in the future. Now that of course requires that even people who do not know anything about conda packaging could do so without too much trouble. I'm writing up a blog post (or possibly a couple) about how to upload to typst-forge, so I'll also open some issues along the way about what I think are the trivial stumbling blocks.

---

So the first one is the preview patching. I have never done a patch myself, so even for me who's packaged a few things on conda-forge, this would require some additional context. When it's just for the package's own preiew import, do you reckon it is something that could be written with a script which could then be run with a simple pixi command (pixi run patch-preview)? I imagine some basic regex magic could do the job.

I'd guess a bit more information would be needed if other things would need patching, but I think that could wait for later.

[freundTech]

Currently, the easiest way to create a correct patch is to make the change to the upstream repo, create a commit and then run git format-patch HEAD~1. After that, you can undo your commit.

Another alternative would be patching with sed during the build process, as is done here: https://github.com/freundTech/typst-forge/pull/27/files#diff-704d37f5fb3efe263f0640def5e66a706952b2f64d3be058eef1eaf7856ecd24R18-R19, but I prefer a patch file, as it's more robust.

Usually, you only need to patch the import to the package itself in a package template. If you want to import other packages from typst-forge instead of universe, you also need to patch them (That's currently not really a concern, as typst-forge has barely any packages, but long term it might be preferable to have typst-forge packages only import other typst-forge packages).

I'll get to your other issues and PRs soon, but I want to do some general changes to the repo first, as I've kind of abandoned it for a few months because I was busy with my master's thesis.

[roaldarbol]

Haha, no worries! I handed in my PhD thesis two months ago, so I feel you!

While I do get that patches are more robust, I think could be a real hurdle for adoption (at least it has seemed daunting to me!). I do like the sed solution - I'll use that for blog post (I'll use it in a PR for #33 too).

PS Are you in the prefix.dev discord, or could you enable discussions here - I'd love to hear about your thoughts about typst-forge. :-)

[freundTech]

I'm freundTech in both the prefix.dev and the typst discord.
But I also just enabled discussions in this repo.