| Summary: | Add support to bitbake fetcher to fetch files from bare repos for PREMIRRORS | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Jeff Polk <jeff.polk> |
| Component: | bitbake | Assignee: | Robert Yang <liezhi.yang> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | corneliux.stoicescu, mark.hatle, mark.hatle, poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Jeff Polk
2013-03-25 02:16:58 UTC
Doesn't this work already in master? I'm struggling to believe this doesn't work with current master since everything in DL_DIR exists as bare git repos and the mirror tarballs are even bare git repos. I'm closing this as WORKSFORME since I can't see the problem here. If there is a problem, please repoen with more details. Inside bitbake/lib/bb/tests/fetch.py I see:
self.d.setVar("PREMIRRORS", "git://someserver.org/bitbake git://git.openembedded.org/bitbake \n")
Marking this as VERIFIED.
I'm reopening this. I found the missing piece of information. The request is not to mirror bare repositories. The request is to mirror -files- -from- bare repositories. In otherwords, if I have a git repository of all of the downloads. I shouldn't have to git clone meta-downloads, and then point the PREMIRRORS to 'file://...meta-downloads'. Instead I should be able to point the PREMIRRORS to 'git://...meta-downloads.git;branch=daisy' It will then get a PREMIRROR call and attempt to extract just the requested file(s) from the bare git repository. Hi Mark, I hadn't seen this until now. The fetcher is "dumb" in some senses, in particular it doesn't know anything about the content of the git repo. This sounds like you want the fetcher to optionally fetch the repo, then unpack it and see if it contains something else which looks like an artefact (either another repo or tarball) which can then be passed back to the original "fetch". I'm not sure this recursive fetching is something we want to support or encourage to be quite honest. If you did want to do it, I'd suggest a different fetcher module for it using a different url type to distinguish it from the "normal" git fetcher. That backend would get calls in from the premirrors code and it would be up to it how it dealt with them. As such, this isn't something I'm planning to work on though and I am not sure how feasible this is, just thinking out loud for anyone who may want to try implementing it. This was REOPENED Just so it's clear, I'm still tracking this. Even though it is in a future state. Mark, it's been 2 years, are you still tracking this? Yes I am. Robert, do we still want this bug opened or has it been fixed? Robert, do we still care about this ER ? No activity so declaring obsolete. |