Opened 15 years ago
Closed 15 years ago
#20625 closed enhancement (wontfix)
subversion: add +xcode variant to use MacPorts subversion in Xcode
| Reported by: | nathan@… | Owned by: | danielluke (Daniel J. Luke) |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 1.7.1 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), 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 (5)
comment:1 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Owner: | changed from macports-tickets@… to dluke@… |
| Summary: | [subversion] "xcode" variant to use MacPorts subversion in Xcode → subversion: add +xcode variant to use MacPorts subversion in Xcode |
comment:2 Changed 15 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 15 years ago by ryandesign (Ryan Carsten Schmidt)
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.
comment:5 Changed 15 years ago by danielluke (Daniel J. Luke)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
As an alternative, you could probably do some DYLD_* environment magic to make xcode look at ${prefix} for libraries.
We're not going to be messing around with apple-installed libraries.
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.