On Mon, Oct 07, 2019 at 03:15:02PM +0100, Ankur Sinha wrote: > Out of curiosity, what workflow do existing package maintainers user > while packaging new software? Is it `fedpkg` based with a folder for the > spec to work in? (I still use rpmbuild + mock/koji-scratch builds). I'm only a packager since about 1.5 weeks or so, so I'm still in the process of getting used to fedpkg. Currently I use a mix of fedpkg and rpmbuild (which I probably will keep for now, as it's kinda convenient). On my system the dist-git lives in ~/rpmbuild/SOURCES.packagename, and SOURCES link to SOURCES.currentpackageiamworkingon. SPECS link to SOURCES. Although I have to re-symlink SOURCES everytime I work on a different package I can use all of rpmbuild, mock, fedpkg,… from the same source folder. Currently I'm only maintaining one package inside the fedora environment, but as I usually refuse to install anything to the system which is not tracked by the package manager I've got a few packages for cases when I need a custom patch or I need a newer version than available via dnf. For that symlinks works quite well. ~astra
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
