[MacPorts] #46029: port submission: qtchooser

MacPorts noreply at macports.org
Fri Dec 12 08:55:44 PST 2014


#46029: port submission: qtchooser
--------------------------+--------------------------------
  Reporter:  rjvbertin@…  |      Owner:  macports-tickets@…
      Type:  submission   |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.3.3
Resolution:               |   Keywords:
      Port:  qtchooser    |
--------------------------+--------------------------------

Comment (by rjvbertin@…):

 > And how exactly would that happen?

 Exactly the same way as the other patches could no longer work.

 > No. The destroot phase is run without superuser privileges. If the
 makefile changes suddenly stops using `INSTALL_ROOT`, the destroot phase
 will try to install files outside of the destroot and will fail. (This is
 one of the reasons we discourage users from setting “macportsuser root” in
 their macports.conf.)

 Admin users can also have permissions to write in places where they better
 know what they're doing.
 I for one have long used MacPorts as myself, and only started sudoing the
 install step when I realised that some things do have to be installed as
 root. That means that /opt/local is still admin-group-writable.
 That may not be a supported configuration, but it is one I keep in mind (I
 have a hunch I might not be the only one doing things that way).


 > Okay. I assume you’ll scour the destroot every single time you muck with
 the port to make sure all the files are always in exactly the right place,
 then.

 Guess how I found the destdir thing?

 With my own ports (the ones I tweak and/or develop), I always run up to
 the destroot step as myself, often also doing the configure or even patch
 step first, in order to move the srcdir to a place where it won't be
 removed by port if I don't pay attention.
 So yes, I have a habit of checking the destroot for pending changes before
 applying them.

 > I frankly don’t see a good reason here.

 Same here - I don't see a good reason to make things more complex. But as
 said, I have contacted the developer to see what can be done with the
 buildsystem to streamline things, e.g. by passing parameters to make.

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


More information about the macports-tickets mailing list