rpm doesn't install hard linked symlinks correctly
Bug #913572 reported by
Jeff Johnson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RPM |
Confirmed
|
Low
|
Jeff Johnson | ||
PLD Linux |
New
|
Undecided
|
Unassigned |
Bug Description
PLD has discovered that rpm doesn't handle hard linked
symlink installation correctly.
Likely affects all versions of RPM everywhere.
tags: | added: pld rpmbuild |
Changed in rpm: | |
status: | New → Confirmed |
Changed in rpm: | |
importance: | Undecided → Low |
assignee: | nobody → Jeff Johnson (n3npq) |
To post a comment you must log in.
justification from pld-devel mail
On 01/09/2012 01:11 AM, Jeffrey Johnson wrote:
This is a hard link to a symlink which is pretty obscure functionality.
nevertheless, it's quite useful when optimizing for packaging speed
when you develop huge packages, you would appreciate faster repackaging
so instead of copying data from %build -> %install tree, one can do hardlinks to speedup the process:
cp -l build.txt $RPM_BUILD_ ROOT/cp- test && l=l && rm -f $RPM_BUILD_ ROOT/cp- test ROOT%{_ appdir}
cp -a$l bin help lib license plugins $RPM_BUILD_
here it makes feature test if srcdir and $RPM_BUILD_ROOT are same disk, and enables hardlinking
now if there is a symlink in a tree, it gets affected by this bug.
also: in rpm package there is packaged only one instance of the hardlink (one in $RPM_BUILD_ROOT),
imho should decide on that actual number, not what it sees from filesystem