Re: Specifying multiple executable arguments using startupitems

2020-08-01 Thread Steven Smith
Not a bug. I just followed what Ryan did and everything is working. Thanks. Here’s the PR: https://github.com/macports/macports-ports/pull/7917 > On Aug 1, 2020, at 9:13 AM, Steven Smith wrote: > > I’m trying to update port clam-server to the new syntax, and am hitting the > following issue.

Re: Specifying multiple executable arguments using startupitems

2020-08-01 Thread Steven Smith
I’m trying to update port clam-server to the new syntax, and am hitting the following issue. As far as I can tell, it looks like a bug. The command `port destroot clam-server` with Macports 2.6.3 fails with this error: > ---> Creating launchd control script 'ClamavScanOnAccess' > Error: Failed

Re: Specifying multiple executable arguments using startupitems

2020-07-30 Thread Ryan Schmidt
On Jun 14, 2020, at 16:08, Ryan Schmidt wrote: > On Jun 14, 2020, at 11:45, Ryan Schmidt wrote: > >> Is this a bug? > > On the assumption that it is, I believe this is the fix: > > https://github.com/macports/macports-base/pull/191 The bug has been fixed in 2.6.3. Some ports will need to adjus

Re: Specifying multiple executable arguments using startupitems

2020-06-16 Thread Joshua Root
On 2020-6-15 03:04 , Steven Smith wrote: > Could be a bug. Widespread practice is to code around it and edit the > launchd .plist’s in the post-activate block. If there's a bug, report it. It could have been fixed months ago and the practice wouldn't have needed to become widespread. - Josh

Re: Specifying multiple executable arguments using startupitems

2020-06-14 Thread Ryan Schmidt
On Jun 14, 2020, at 11:45, Ryan Schmidt wrote: > Is this a bug? On the assumption that it is, I believe this is the fix: https://github.com/macports/macports-base/pull/191

Re: Specifying multiple executable arguments using startupitems

2020-06-14 Thread Ryan Schmidt
On Jun 14, 2020, at 12:24, Ryan Schmidt wrote: > On Jun 14, 2020, at 12:18, Steven Smith wrote: > >>> If startupitem support in MacPorts base is not sufficient to express what >>> we need, it should be enhanced. >> >> That’s a good objective. The current startupitems behavior annoyed me until

Re: Specifying multiple executable arguments using startupitems

2020-06-14 Thread Ryan Schmidt
On Jun 14, 2020, at 12:18, Steven Smith wrote: >> If startupitem support in MacPorts base is not sufficient to express what we >> need, it should be enhanced. > > That’s a good objective. The current startupitems behavior annoyed me until I > just learned to copy what others had done to code

Re: Specifying multiple executable arguments using startupitems

2020-06-14 Thread Steven Smith
> If startupitem support in MacPorts base is not sufficient to express what we > need, it should be enhanced. That’s a good objective. The current startupitems behavior annoyed me until I just learned to copy what others had done to code around it. I’d also note that doing a `man launchd.plist`

Re: Specifying multiple executable arguments using startupitems

2020-06-14 Thread Ryan Schmidt
On Jun 14, 2020, at 12:04, Steven Smith wrote: > Widespread practice is to code around it and edit the launchd .plist’s in the > post-activate block. You can use tcl’s reinplace or sh’s plutil as necessary > to edit the .plists. > > Example Portfiles that do this extensively: > > • > https