| Summary: | bitbake requires vi on the host (debian jessie does not have a vi package) | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Todor Minchev <todor.minchev> |
| Component: | core | Assignee: | brian avery <brian.avery> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | brian.avery, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | 2.3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Todor Minchev
2017-03-17 21:57:44 UTC
It does, generally installed via vim-tiny. You must have built a fairly minimal system to not have vi present. I can't recall what recipe needed vi, but maybe we should move it to the nonfatal list. CCing RP as I suspect he can remember what recipe wanted vi. the cvs build which is part of the sdktest in meta/lib/oeqa/runtime/cases/buildcvs.py needs it when it configures cvs (cvs wants an editor for messages). i have a switch to use cpio as the sdktest which I'll send in once i can test it. then we can drop vi from the list completely. On a separate note, we could consider moving *all* of the testimage requirements to nonfatal or even making a third category HOSTTOOLS_EXTENDED, and warn that some functionality beyond building may fail if the needed programs are not available. patch on ml to switch to cpio. Will take and close if RP ok with the switch. fixed in master: af994bfcfddb2e17d9adc13fd13870731c5ee6c7 We switched the sdk test from cvs (which needed vi) to cpio (which doesn't) |