Changes between Initial Version and Version 1 of Ticket #47755, comment 21
- Timestamp:
- Jun 19, 2015, 8:01:58 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #47755, comment 21
initial v1 9 9 > The method of software distribution (i.e. from a git or hg or svn or cvs or bzr repository, or from a tarball download) should have no bearing on whether a project interferes in some way with MacPorts. You'll have to be more specific about the problem you're experiencing, if you still need help with it, but it sounds like it's not related to this ticket, and if it's something you're doing outside of MacPorts (using "`make`" for example) then it sounds like it's not related to MacPorts. 10 10 11 While my original ticket (#48052) was rightly marked duplicate, it turned out that my inability to install encfs was two-fold . The broken / unregistered symlink from wxWidgets and Git project compilations.11 While my original ticket (#48052) was rightly marked duplicate, it turned out that my inability to install encfs was two-fold -- the broken / unregistered symlink from wxWidgets and Git project compilations. 12 12 13 13 You're right on that it was the "making" that caused the issue, so in certain respects the conflicting software was my fault. That said, Macports does host a Git port, which is a software distribution platform. There is no indication / warning that Git projects involving compilation may install libraries that might interfere with Macports. In my opinion, this echos the debate happening above regarding the dividing line between user and maintainer responsibility. 14 15 Maybe it is warranted that Macports add a disclaimer to the Git port? Or, perhaps a guide to preventing conflicts with Macports when building Git projects?