Bug 1462182 - RFE: look-aside cache
RFE: look-aside cache
Status: NEW
Product: Copr
Classification: Community
Component: backend (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: clime
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 07:47 EDT by Michael Mráka
Modified: 2017-07-18 05:17 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Mráka 2017-06-16 07:47:07 EDT
Description of problem:
In Spacewalkproject we need to build thirdparty packages with a custom options or custom patches.

In such cases we store only package spec and patches in git repo because storing source tgzs in git is not efficient.   

To build the package we need to have a place (look-aside cache) where we can upload tgz and copr will find it during build. It could be the same place where copr puts sources when building from srpm or url.
Comment 1 Pavel Raiskup 2017-06-16 08:13:30 EDT
It is planned to open copr's dist-git for writing, similar to what we have
in Fedora's dist git (upload tarball, and commit only sources/patches to
git), this is bug 1397508.

You could build from Fedora's dist-git too, something to be fixed there
(bug 1391889) but could work for you.

There's tito feature that supports git annex too:
http://m0dlx.com/blog/Reproducible_builds_on_Copr_with_tito_and_git_annex.html

And perhaps you are interested in this too
https://pagure.io/copr/copr/issue/60
Comment 2 clime 2017-07-18 05:17:46 EDT
Could this possibly be also addressed by adding GIT LFS support to COPR? Meaning that the tarballls you need to place in your repo would be links into a storage and COPR would auto-download them?

This seems to be a good way to solve this problem as well.

Note You need to log in before you can comment on or make changes to this bug.