Merge lp:~broder/ubuntu/precise/pkgbinarymangler/relative-symlinks-899520 into lp:ubuntu/precise/pkgbinarymangler
Status: | Merged |
---|---|
Merged at revision: | 228 |
Proposed branch: | lp:~broder/ubuntu/precise/pkgbinarymangler/relative-symlinks-899520 |
Merge into: | lp:ubuntu/precise/pkgbinarymangler |
Diff against target: |
134 lines (+66/-9) 3 files modified
debian/changelog (+8/-1) pkgstriptranslations (+54/-4) test/run (+4/-4) |
To merge this branch: | bzr merge lp:~broder/ubuntu/precise/pkgbinarymangler/relative-symlinks-899520 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pitt | Approve | ||
Review via email: mp+85308@code.launchpad.net |
Description of the change
This merge adds a helper function for generating Policy-compliant symlinks to pkgstriptransla
The original merge was right, but only by accident.
I used "<" instead of "<=" in two of the for loops. It turns out, though, that dh_link was using the $# sigil, which means "the index of the last element of the array" - i.e. "length minus 1", so "<" instead of "<=" is actually correct. Now that I've fulfilled my daily quotient of Perl insanity, I added a comment so that other people could follow along.
On further investigation, I realized the symlinks it was generating were right. Because the foo -> foo-langpack symlinks are between files at the same hierarchy level, you can verify that the symlinks are correct by noting that the number of ".." entries in the path is the same as the number of non-".." entries.
Thank you!