| Summary: | cvs is required to be installed on host to support cvs SRC_URI | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Chen Qi <Qi.Chen> |
| Component: | devtools / tool chain | Assignee: | Ross Burton <ross.burton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | mark.hatle, meta.mr.watcher, meta.watcher, poky.doc.watcher, poky.watcher, randy.macleod, ross.burton, sgw, srifenbark |
| Version: | 2.1 | ||
| Target Milestone: | 2.2 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 29 July 2016: Set documentation flag to "No" | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Chen Qi
2016-07-07 07:16:38 UTC
Or, remove that recipe so there's no cvs recipes in oe-core. Hi, I changed the doc flag to "Don't Know" here as it looks like depending on which track you take the docs might or might not be affected. Let me know if we want to require this package or if we are going to remove the recipe. Thanks, Scott Mark, would removing the RPM recipe that fetched from CVS be a problem for you, or do you usually work on tarballs and patches instead of upstream's CVS directly? oe-core 0cb5c06ea12c9070f19045cc82fc6276bfad3970 removed the RPM recipe that fetched from cvs, so there's no more CVS-fetching recipes in oe-core. Setting the doc flag to "No" as it looks like the need disappeared. Scott |