https://bugzilla.redhat.com/show_bug.cgi?id=2130607 --- Comment #17 from Alexander Ploumistos <alex.ploumistos@xxxxxxxxx> --- (In reply to Sébastien Le Roux from comment #14) > Ok so here I do have some questions, if I tag a release, then I noticed > that everything inside the repo is packaged into a single acrive, but the > repo contains > other stuff that only Fedora RPMs data, not only that but it seems to me > that to work > this method would require the repo to host the files of the GNU tarball, > so that when I create a release it will create the tarball required to build > the RPM ... A small comment about the split I mentioned earlier: As a developer who wants their program to build on linux, your responsibilities stop at providing a way for people to build the program on any random distribution. In the case of Atomes, there are only files that go under /usr/bin and /usr/share, which are pretty much standard locations on almost every distribution and that simplifies the life of a distro maintainer. So all you need to worry about is that after e.g. a ./configure make make install the program would compile successfully and the files would end up in reasonable places. As a package maintainer, your job is to tailor the package to the specifics of a/your distribution, i.e. make sure dependencies are satisfied, follow the distro's guidelines, use distro-specific tools and all that. Your developer self should do their development only in the Atomes repository and stop there. Your Fedora package maintainer self would then create the Atomes-rpm-build or Atomes-GNU repository in the distribution's dist-git (src.fedoraproject.org). Of course, all of the above is just a suggestion, you do whatever works for you. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2130607 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue