Closed jdemeyer closed 8 years ago
Description changed:
---
+++
@@ -1 +1 @@
-The packages `fricas`, `frobby`, `gap3` use non-standard patching.
+The packages `fricas` and `frobby` use non-standard patching.
I think that fricas shouldn't need the patch anymore, at least with #21377 (but I admit, I cannot package)
Cc'ing dimpase, who probably has a script that created the frobby patches.
Replying to @mkoeppe:
Cc'ing dimpase, who probably has a script that created the frobby patches.
no, I think I simply used git to create/update patches.
Otherwise, this simply moves things around, right?
This ticket edits the patch to make it -p1 instead of -p0 Wouldn't it be better if there was a public git of the modified frobby, and a script that regenerated the patches?
I don't think that we ever use scripts in Sage to generate patches...
I know that we don't (with some exceptions), but my point is that it would be better if we did.
Our patch management seems ad-hoc (in contrast for example to Debian's tools and documented workflow for this)
and few people seem to be aware of git format-patch
, which can be used to create a set of patches.
Nice. Let's add a short section on how to manage patchsets with git format-patch to the developers' guide...
This is #21781.
Reviewer: Matthias Koeppe
Changed branch from u/jdemeyer/standardize_patches_in_fricasfrobbygap3 to 683e7b9
The packages
fricas
andfrobby
use non-standard patching.CC: @embray @dimpase
Component: packages: experimental
Author: Jeroen Demeyer
Branch/Commit:
683e7b9
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/21721