| Summary: | Add documentation for package installation during runtime testing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Documentation] Reference | Reporter: | Mariano Lopez <mariano.lopez> | ||||
| Component: | handbook | Assignee: | Scott Rifenbark <srifenbark> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | Medium | CC: | joshuagloe, mariano.lopez, poky.doc.watcher, poky.watcher, srifenbark | ||||
| Version: | 2.2 | ||||||
| Target Milestone: | 2.2 M4 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | 7 June 2016: ACCEPTED | ||||||
| OS type for building Yocto: | --- | Type of Regression: | New (Never tested) | ||||
| Verified: | Documentation change: | Done (doc changes complete) | |||||
| Bug Depends on: | |||||||
| Bug Blocks: | 7850 | ||||||
| Attachments: |
|
||||||
|
Description
Mariano Lopez
2016-05-24 20:46:48 UTC
The docs note that "permissions and special attributes will be lost". Is there a plan to support permissions and attributes in exported tests? I can certainly imagine test cases that would fail if the permissions and extended attributes on files from the package weren't correct. Yes, there is a requirement for that. I was thinking in using tar to accomplish this, the drawback is tar would be needed in the DUT. Right now I'm really open to suggestion on how to do this. Had a conversation with Joshua, he recommends using rsync in order to solve the permission/attributes issues when using scp. Unfortunately rsync requires the binary to be installed in both machines, so it is the same problem as having tar in the DUT. (In reply to comment #4) > Unfortunately rsync requires the binary to be installed in both machines, so > it is the same problem as having tar in the DUT. Hmm, right. I think tar is probably our best option at this point, then. I'm not sure the busybox tar is up to it, though perhaps we could first copy over a (perhaps even statically linked) tar (bsdtar, or GNU tar) and use that? Setting to ACCEPTED. See these sections: * http://www.yoctoproject.org/docs/2.2/dev-manual/dev-manual.html#exporting-tests * http://www.yoctoproject.org/docs/2.2/dev-manual/dev-manual.html#installing-packages-in-the-dut-without-the-package-manager Note that in the DUT section (second link above) I did not create widowed sections. All the information is folded into a single section. If you don't have multiple subsections then you don't want to create a single one. Please review and let me know if this is good. I swear I fixed this before and put a comment in Bugzilla regarding this bug. I don't know where it went though. Scott Just two comments, In the second section, the phrase " Furthermore, the filename must map directory to the test module name with a .json extension.", instead of directory it is directly. And in the JSON example the first "foo" is missing. Thanks I know this is an aside, maybe we have/need a different bugzilla entry for this? (In reply to comment #4) > Unfortunately rsync requires the binary to be installed in both machines, so > it is the same problem as having tar in the DUT. I happened to be looking over the rsync manpage earlier and it states multiple times that rsync can be used "over any remote shell" -- what makes you think the rsync binary is required on both machines? (In reply to comment #9) > I know this is an aside, maybe we have/need a different bugzilla entry for > this? I just opened bug 9848 to track this. Ok - Sorry about that. I fixed these up - see http://www.yoctoproject.org/docs/2.2/dev-manual/dev-manual.html#installing-packages-in-the-dut-without-the-package-manager Can we set status to RESOLVED for this bug now? Thanks, Scott Indeed, thanks Scott Thanks... setting to RESOLVED and sticking the doc flag at "done." Scott |