I think MockSCM is that what you need. ----- Original Message ----- > From: "Martin Novák" <[email protected]> > To: [email protected] > Sent: Sunday, April 17, 2016 5:38:48 PM > Subject: Packaging upstream with released tarballs in Copr > > Hello, > > It appears there's currently no option to build a package by just a > SPEC file which contains valid Source0 URL. > > There's a project on GitHub with released tarballs, which I'd like to > package in Copr (and later in Fedora perhaps). The easiest method for > building that package in Copr for me would be to link a SPEC file from > my GitHub repository which I'd regulary update with new project > releases.* > > Copr however offers only Tito and Mock SCM builds. From what I read, > it seems to me that both methods expect upstream and packaging files > to be in same repository. Is it true? If not, is there any example of > a Tito/MockSCM project linking external tarball which builds on Copr? > > If yes, then maintaining a forked repository seems a bit cumbersome to > me. For each release Git tag in the upstream repository, I'd have to > create a new child tag for the release with a SPEC file and it doesn't > seem Tito automates this case so I'd have to cherry-pick the SPEC file > from my master branch and modify it. Of course I can automate this > with a script also in my master branch, but it feels "custom" to me. > Is there any proper method? > > > Even though I've researched the topic I'm still newbie to packaging > and Git so please have mercy. > > Thank you. > > > * Or linking repository and specifying subdirectory and SPEC file name > so that the repository could contain more projects and a project > could contain patches. > _______________________________________________ > copr-devel mailing list > [email protected] > https://lists.fedorahosted.org/admin/lists/[email protected] >
-- -Igor Gnatenko _______________________________________________ copr-devel mailing list [email protected] https://lists.fedorahosted.org/admin/lists/[email protected]
