Summary: | [TRACKER] Packages installing files u-w | ||
---|---|---|---|
Product: | Quality Assurance | Reporter: | Michał Górny <mgorny> |
Component: | Trackers | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | tdalman |
Priority: | Normal | Keywords: | Tracker |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 554342, 554350, 554360, 554362, 554364, 554372, 554374, 554260, 554264, 554340, 554344, 554346, 554348, 554352, 554354, 554356, 554358, 554366, 554368, 554370 | ||
Bug Blocks: |
Description
Michał Górny
2015-07-08 19:15:26 UTC
Can you provide an explanation we can copy/paste for upstream bug reports please? This is an issue that does not seem to affect installation from most upstream sources. install(1) from coreutils unlinks the destination file if it exists; therefore, the mode of the installed file does not matter at all. Perhaps portage should be adjusted to unlink existing files when merging them onto ROOT if it does not do so already. > While the issue is not immediately noticeable since usually all write operations on those files (e.g. stripping) are done as root.
Oh, I see. We are talking about operations that may also be performed during/after src_install, not necessarily during the merge phase.
|