On Tue, 15 Oct 2024 17:29:42 +0000 James Addison <j...@jp-hosting.net> wrote: > On Tue, 15 Oct 2024 at 16:03, Soren Stoutner <so...@debian.org> wrote: > > > > Typically, in Debian packaging, you would use Files-Excluded in debian/ > > copyright to remove things like vendored library code, and debian/patches to > > make modifications that have not yet/are not likely to be accepted upstream. > > Thank you, Soren. I'm considering what to do about this. > > In some ways it would be nice to solely use patches and > file-exclusions for the Debian packaging here -- on the other hand, if > I want to develop and forward future modifications to upstream (and > that, I think, will be my default approach, even if the patch > acceptance rate is unpredictable), then the standard GitHub workflow > is to initiate those as pull requests from fork(s) of the source. > > Additionally, I have in mind that I don't think it's yet clear in this > case whether my fork is a continually and actively maintained > development derived from the original (a clear candidate for upstream > status), or simply a place where a few patches have been applied and > collected (a more ambiguous situation). > >
Hi James, Have you made any progress on how you wish to proceed with the package? Regards Phil -- Donations... Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg Threads: https://www.threads.net/@kathenasorg --
signature.asc
Description: This is a digitally signed message part
