Hi, Andy Tai <a...@atai.org> writes:
> Hi, if I have package a and b. A is a dependency for b or b depends on a, > and b has a patch that has to be applied to A's sources to build b. But > B's patch is not something a would accept. How would b be packaged in > guix? Make a custom a-for-b to support b? Yes. Example at hand: ffmpeg-jami, which includes patch currently not acceptable to upstream (IIRC), same for pjproject-jami. It's a suboptimal situation though, so ideally the parties having made a patch should go the extra mile of meeting upstream requirements for having it accepted upstream, as it makes life for packagers much less enjoyable, not to mention it means they have to rebase the patch forever. > B's patch for a will never go upstream but can that patch be kept in > guix's patch directory? Normally guix's patch directory means patches > not yet merged upstream. Not always. Some patches are Guix-specific and not meant for being upstreamed (for example, removing the FHS directories being consulted/hard-coded in the source to ensure the host does not interfere). -- Thanks, Maxim
