| Summary: | [rpm/zypper] remove_packaging_data_files makes rpm/zypper install/remove not work in minimal image | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Jiajun Xu <jiajun.xu> |
| Component: | core | Assignee: | Qing He <qing.he> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | ke.yu, kevin.tian, kunwei.tian, meta.mr.watcher, meta.watcher, richard.purdie, sgw, yi.zhao |
| Version: | unspecified | ||
| Target Milestone: | 1.0 M4 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Jiajun Xu
2010-12-21 19:08:13 UTC
If packaging files are removed, its expected that zypper and rpm won't work. The question is therefore should the packaging files be removed on a minimal image? So we have a definition anywhere which states this one way or another? Should rpm and zypper be installed on the minimal image? And maybe we can add a check on the rootfs stage to increase sanity /var/lib/rpm/* is only removed iff some variable (say, ROOTFS-PRUNE-PKG-INFO = "1") is set and rpm/zypper is not installed Since the package data files are removed by the explicit call to remove_packaging_data_files, rpm and zypper should not be installed in the minimal image as that makes no sense. Being able to set an option to remove the packaging files which only worked if rpm/zypper were not installed would not be intuitive to the user. Having a check in remove_packaging_data_files that ensures rpm/zypper/dpkg/apt/opkg are not installed would be nice though. fixed by RP in commit 36f8aa6dc8971119ad35e7d581092fd05a2d45a3 (In reply to comment #4) > fixed by RP in commit 36f8aa6dc8971119ad35e7d581092fd05a2d45a3 Verify the bug since with M4 RC1 build, there is no rpm/zypper command in minimal image now. |