[MacPorts] #35589: Add optional --patch parameter to `port install`
#35589: Add optional --patch parameter to `port install` ----------------------------------------+----------------------------------- Reporter: chocolate.camera@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Keywords: | Port: ----------------------------------------+----------------------------------- Add an optional argument to the `install` command to apply a patch before compiling. Building custom versions of a port is a pain when it could perfectly be automated considering the procedure is always identical.[[BR]] 1. Open the port's Portfile directory[[BR]] 2. Create the `files` subdirectory[[BR]] 3. Copy the patch into it[[BR]] 4. Edit the `Portfile` file and add the `patchfiles` directive.[[BR]] 5. Execute the command `port install portname` Most of 1-4 cannot be done with the Finder or most Cocoa editors since those actions require root (or sudo). It would nicer to be able to do it on 1 stroke at install time with a command-line argument: sudo port install portname --patch /path/to/myPatch Or is there a similar way that I am missing? -- Ticket URL: <https://trac.macports.org/ticket/35589> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35589: Add optional --patch parameter to `port install` ----------------------------------------+----------------------------------- Reporter: chocolate.camera@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Keywords: | Port: ----------------------------------------+----------------------------------- Changes (by ryandesign@…): * type: request => enhancement Old description:
Add an optional argument to the `install` command to apply a patch before compiling.
Building custom versions of a port is a pain when it could perfectly be automated considering the procedure is always identical.[[BR]]
1. Open the port's Portfile directory[[BR]] 2. Create the `files` subdirectory[[BR]] 3. Copy the patch into it[[BR]] 4. Edit the `Portfile` file and add the `patchfiles` directive.[[BR]] 5. Execute the command `port install portname`
Most of 1-4 cannot be done with the Finder or most Cocoa editors since those actions require root (or sudo).
It would nicer to be able to do it on 1 stroke at install time with a command-line argument:
sudo port install portname --patch /path/to/myPatch
Or is there a similar way that I am missing?
New description: Add an optional argument to the `install` command to apply a patch before compiling. Building custom versions of a port is a pain when it could perfectly be automated considering the procedure is always identical.[[BR]] 1. Open the port's Portfile directory 2. Create the `files` subdirectory 3. Copy the patch into it 4. Edit the `Portfile` file and add the `patchfiles` directive. 5. Execute the command `port install portname` Most of 1-4 cannot be done with the Finder or most Cocoa editors since those actions require root (or sudo). It would nicer to be able to do it on 1 stroke at install time with a command-line argument: {{{ sudo port install portname --patch /path/to/myPatch }}} Or is there a similar way that I am missing? -- Comment: I think our answer to this use case is for the user to [http://guide.macports.org/#development.local-repositories create a local copy of the Portfile] with whatever modifications they want. -- Ticket URL: <https://trac.macports.org/ticket/35589#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35589: Add optional --patch parameter to `port install` ----------------------------------------+----------------------------------- Reporter: chocolate.camera@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Keywords: | Port: ----------------------------------------+----------------------------------- Comment(by chocolate.camera@…): I wrote the feature request precisely after reading that, and considering it a pain. I think that it should be more handy that Macports itself handled that by using a command-line parameter. My need for it is not so much because it would be useful to **me**, but that it would be easier for me to tell other non-Terminal-savvy users how to install a custom port by simply sending them the patch and giving them the command line to execute. The suggested method is completely out of those user's abilities. -- Ticket URL: <https://trac.macports.org/ticket/35589#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts