On Dom, 2016-04-17 at 11:50 -0400, Igor Gnatenko wrote:
I think MockSCM is that what you need.
Here is a very good example of using MockSCM https://fedoraproject.org/
wiki/Projects/Mock/Plugin/Scm#Example , but looks to me that is useful
for developers of the source of one package ...
I'd like to, as packager maintainer, avoid upload tarball every time I
change my spec, for example, I'm packaging opencv-3.1, when I just
modify two or three letters in opencv.spec, I have to do :
rpmbuild -bs opencv.spec --define "_sourcedir ." --define '_srcrpmdir
.' && copr-cli build sergiomb/opencv ./opencv-3.1.0-3.fc23.src.rpm
and I have to upload 123M every time , I think that is that Martin (and
me ) want to avoid .
----- Original Message -----
> From: "Martin Novák" <mtnvk(a)seznam.cz>
> To: copr-devel(a)lists.fedorahosted.org
> Sent: Sunday, April 17, 2016 5:38:48 PM
> Subject: Packaging upstream with released tarballs in Copr
> 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
> package in Copr (and later in Fedora perhaps). The easiest method
> building that package in Copr for me would be to link a SPEC file
> my GitHub repository which I'd regulary update with new project
> Copr however offers only Tito and Mock SCM builds. From what I
> it seems to me that both methods expect upstream and packaging
> to be in same repository. Is it true? If not, is there any example
> a Tito/MockSCM project linking external tarball which builds on
> If yes, then maintaining a forked repository seems a bit cumbersome
> me. For each release Git tag in the upstream repository, I'd have
> create a new child tag for the release with a SPEC file and it
> seem Tito automates this case so I'd have to cherry-pick the SPEC
> 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
> 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
> so that the repository could contain more projects and a project
> could contain patches.
> copr-devel mailing list
Sérgio M. B.