Ticket #20625 (closed enhancement: wontfix)
subversion: add +xcode variant to use MacPorts subversion in Xcode
| Reported by: | nathan@… | Owned by: | dluke@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 1.7.1 |
| Keywords: | Cc: | ryandesign@…, nathan@… | |
| Port: | subversion |
Description
It would be handy if the subversion port had an "xcode" variant which symlinked all the required files in /usr/lib to the relevant files under /opt/local/lib. These files are:
libapr-1.dylib libaprutil-1.dylib libsvn_client-1.dylib libsvn_delta-1.dylib libsvn_diff-1.dylib libsvn_fs_fs-1.dylib libsvn_fs-1.dylib libsvn_ra_local-1.dylib libsvn_ra_svn-1.0.dylib libsvn_ra-1.dylib libsvn_wc-1.dylib libsvn_repos-1.dylib libsvn_subr-1.dylib
Change History
comment:1 Changed 4 years ago by ryandesign@…
- Cc ryandesign@… added
- Owner changed from macports-tickets@… to dluke@…
- Summary changed from [subversion] "xcode" variant to use MacPorts subversion in Xcode to subversion: add +xcode variant to use MacPorts subversion in Xcode
comment:2 Changed 4 years ago by nathan@…
What do you mean by "proper"? In lieu of changes to Xcode by Apple, this is the only way to integrate Xcode with the MacPorts version of Subversion.
comment:4 Changed 4 years ago by ryandesign@…
It is a fundamental principle of MacPorts that it does not interfere with your Apple-provided software. The way this is accomplished is that MacPorts software is supposed to be confined to its own prefix (e.g. /opt/local). There are some exceptions but in general this is true.
The variant you propose would interfere with Apple-provided software. First, replacing the system's svn libraries would interfere with the system's svn program. And if you were to uninstall the subversion port, it would leave your system's Subversion completely nonfunctional.
It would not be proper for MacPorts to install files in /usr, and certainly not for MacPorts to modify files installed by the operating system.