#44509: selfupdate tried to tell me to run selfupdate again ---------------------+-------------------------------- Reporter: dave@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: selfupdate Port: | ---------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:2 dave@…]:
MacPorts could write out a tiny trampoline program to /tmp, make it unwritable then setuid root, exec the trampoline, then the trampoline execs (the new) MacPorts, which deletes the trampoline program and continues. Code to do this is probably in a library somewhere, or it should be.
That sounds plausible. Someone should write code to do this and see what happens. Or we may want to instead implement SummerOfCode#self-management
This trick would not only solve the problem posed in this report, but it would allow selfupdate to become an option, not a command to be run by itself and waited for.
An option... are you suggesting that instead of updating MacPorts by running "sudo port selfupdate", they would update by running, to pick a flag at random, "sudo port -z"? Why would this be an improvement? I would prefer the above-suggested improvement, that it would be updated by running "sudo port upgrade MacPorts". -- Ticket URL: <https://trac.macports.org/ticket/44509#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X