On Mon, Dec 28, 2020 at 2:21 PM Derek Pressnall <derekp7@xxxxxxxxxxxxxxxx> wrote: > (snip) Welcome to Fedora! > > Meanwhile, a couple additional questions. Right now I have a template > of the spec file in the project's Git repo. Should the spec file be > in its own repo (or possibly an orphaned branch of this repo)? That > way all packaging-specific items can be versioned separately from the > app itself. > > Secondly, I'll put the above Makefile modifications in shortly, but it > may be a bit before the next posted release of Snebu. So for the > purpose of the RPM, should I put them in as patches (that are owned by > the rpm) until the next Snebu release comes out? > > Thanks. Since you're aiming to submit the package as an official Fedora package, the .spec file should not live upstream. For Fedora packages, the Fedora dist-git repository is considered the "source of truth" for a package's .spec files: https://docs.fedoraproject.org/en-US/packaging-guidelines/#_spec_maintenance_and_canonicity So you actually shouldn't track the .spec file in the upstream project's git repo, but use the official git repo provided for every Fedora package instead. As for the second question, yes, a .patch file sounds like the best way to do that until the next release has those changes. Fabio (decathorpe) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
