Bugzilla – Full Text Bug Listing
| Summary: | [eclipse-build] Make symlink to eclipse.ini relative | ||
|---|---|---|---|
| Product: | [Tools] Linux Tools | Reporter: | Andrew Overholt <overholt> |
| Component: | eclipse-build | Assignee: | Krzysztof Daniel <krzysztof.daniel> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | 1.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Actually why should it be relative? I don't see this rpmlint warning and having it absolute looks as the right thing in this case. Investigating. Indeed there is no warning, and the eclipse.ini is expected to be in absolute location regardless of where the eclipse is actually installed. Leaving as is with no plan to change. |
The rpmlint tool says that symlinks in an RPM should be relative. For those RPM-based distributions which are using eclipse-build, it would be good if we made the symlink we provide: ${destDir}/usr/lib{,64}/eclipse/eclipse.ini -> /etc/eclipse.ini be relative. Something like this may work: ${destDir}/usr/lib{,64}/eclipse/eclipse.ini -> ../../../etc/eclipse.ini User-specified ${destDir} and such should be taken into account when making this change. Benjamin Drung has verified that the Debian packaging tools will turn a relative symlink such as this into an absolute symlink which satisfies lintian's requirements.