Bug 389251
Summary: | symlinks and packaging | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Florian La Roche <laroche> |
Component: | amsn | Assignee: | Sander Hoentjen <sander> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | mmaslano |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-21 12:42:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 389261 |
Description
Florian La Roche
2007-11-18 11:26:53 UTC
%{libdir}/tcl%{tcl_version} is used to package arch-specific tcl-packages, what is wrong with that? It surely can't go in datadir? what i mean is: the symlink should be an actual dir, not a symlink. This will change with the release of tcl/tk 8.5 Seems like this change is now already done for the 8.4 release. Is /usr/share not possible for this package? regards, Florian La Roche Well, /usr/share is only for arch-independent stuff. Both amsn and tkdnd are arch-dependent, that's why they can't go there. From http://fedoraproject.org/wiki/PackagingDrafts/Tcl which is still a draft, but a good guideline nonetheless: "Tcl extension packages must be installed in %{_datadir}/tcl8.x if they are noarch packages containing only Tcl code, or %{_libdir}/tcl8.x if they are arch-specific extensions containing shared libraries." Ok, seems like the TODO section in the above wiki has all the needed items in it and tcl needs to be fixed first. Thanks a lot, Florian La Roche I'd like to fix all installation path in tcl8.5. I created testing rpm, this problem is related with bug#160441 |