heart Joe (Jun-Yan) Chen reacted to your message:

From: Tomas Kopecek <tkopecek@redhat.com>
Sent: Tuesday, May 30, 2023 12:36:48 PM
To: Koji development <koji-devel@lists.fedorahosted.org>
Subject: [EXT] Re: Question about "The way to maintain RPMs from my own git"
 
No,  you're completely free to set it up. Documentation about how koji is getting all it needs from git checkout is here [1]. Historically (from cvs times) default is to run "make sources" in the checkout, so Makefile is expected to be there. Nevertheless, it can be overridden to any command (e.g. "fedpkg sources" which is standard for Fedora). Of course, any command which will be invoked here must be part of the srpm-build group in buildroot, so it is available at that time. It also answers the second question. You can wire up any logic into this command. If you're looking for some "complete" solution, rpkg/fedpkg [1], [2] is used in Fedora with dist-git.

[1] https://docs.pagure.org/koji/server_howto/#scm-config
[2] https://docs.pagure.org/rpkg/
[3] https://docs.pagure.org/fedkg/


On Tue, May 30, 2023 at 12:13 PM Joe (Jun-Yan) Chen <jychena@ambarella.com> wrote:
Dear Koji development team,

I hope this email finds you well. I have a couple of questions regarding the usage of "koji scm build" and dependency resolution for RPMs. I would greatly appreciate your guidance on these matters.

Question 1:
When using "koji scm build", are there any specific rules that the git must adhere to? For example, does it need to contain a '.spec' file, and should the 'sources' file include an md5 and tarball name? Or is there a possibility to use certain tools or modify certain aspects to enable the building of RPMs from a regular git repository?

Question 2:
Are there any tools available that can help with resolving dependencies for RPMs and automatically fetch the exact source code from my own git repository? I have already written the ".spec" file for my project, but the process of manually retrieving the source code is quite cumbersome. It would be great if there were tools or methods to simplify this process.


Thank you very much for your attention and assistance. I look forward to your response.
      


Best Regards,
Junyan CHEN


Ambarella AI Envisioned Junyan(Joe) CHEN
Software Engineer | SDK Team
Phone: +86-021-60880608-265
Email:  jychena@ambarella.com


This email and attachments contain Ambarella Proprietary and/or Confidential Information and is intended solely for the use of the individual(s) to whom it is addressed. Any unauthorized review, use, disclosure, distribute, copy, or print is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.
_______________________________________________
koji-devel mailing list -- koji-devel@lists.fedorahosted.org
To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
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.fedorahosted.org/archives/list/koji-devel@lists.fedorahosted.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--

            Tomas Kopecek <tkopecek@redhat.com>
            RHEL Build Development, RedHat

This EXTERNAL email has been scanned by Proofpoint Email Protect service.