[MacPorts] #38795: cmake files that weren't installed by the cmake port cause cmake to fail

[MacPorts]

#38795: cmake files that weren't installed by the cmake port cause cmake to fail
---------------------------+--------------------------------
  Reporter:  ozanyarman@…  |      Owner:  macports-tickets@…
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.3
Resolution:  invalid       |   Keywords:
      Port:  cmake         |
---------------------------+--------------------------------

Comment (by ryandesign@…):

 Replying to [comment:18 ozanyarman@…]:
 > I might have spoken just a bit too soon, as I still have to keep
 deleting unproperly linked .cmake files to pave the way for my KDENLIVE
 installation. Macports is dealing with too many broken dependencies on the
 way... With each little progress I keep deleting a bit more and I get
 further. I don't know why so many irrelevant cmake modules are there to
 begin with...

 You should be able to delete all the cmake files that don't belong in one
 go. You could use this to check all of them at once:

 {{{
 port provides /opt/local/share/cmake/modules/*
 }}}

 > Does it make any difference if I keep my macports.conf user as
 '''root'''?

 Using "root" is less secure. The macportsuser is the user MacPorts uses
 when building software. Usually we like to use the "macports" user, which
 is a user MacPorts creates for this purpose, which doesn't have permission
 to modify most of the other files on your system. Whereas if you use
 "root", then while building, MacPorts technically has the ability to do
 ''anything'' to ''any'' of your files. A badly-written (or malicious)
 build or configuration script could inadvertently (or intentionally)
 delete or change your files, or install files you didn't expect that
 aren't tracked by MacPorts. That shouldn't happen, of course, since there
 is a manual human-controlled process for getting new ports and port
 updates into MacPorts in the first place, so any such problems should be
 detected by someone before an update is committed and made available to
 you.

-- 
Ticket URL: <https://trac.macports.org/ticket/38795#comment:19>
MacPorts <http://www.macports.org/>
Ports system for OS X