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.
For example, see: https://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/debian/ copyright?ref_type=heads https://salsa.debian.org/cryptocoin-team/electrum/-/tree/master/debian/ patches?ref_type=heads On Tuesday, October 15, 2024 4:47:44 AM MST James Addison wrote: > Hi Phil, > > On Tue, 15 Oct 2024 at 04:45, Phil Wyett <philip.wy...@kathenas.org> wrote: > > [ ... snip ... ] > > This package uses a fork of the upstream github repo. Is there a particular > > reason for not using it? > > Primarily this is to build against a source that includes additional > modifications, and removes vendored library code (a Debian > best-practice, but also a general software development practice that I > tend to agree with). > > Apart from the vendored-code removal, I've offered each modification > within pull requests to upstream, with mixed results that I expect may > be due to the fact that it isn't worth the time/effort for the > developer to review and apply them all (the game was released nearly a > decade ago, and the developer is working on other titles). > > On a related note: the homepage field for the package contains a > hyperlink to the game's webpage on the developer website, instead of a > link to my fork of the codebase on GitHub. This is somewhat > intentional, because players will require the corresponding game data > (hence the package is assigned to the Debian contrib section), and > that game data is available for purchase from the developer. > > Regards, > James -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
