Re: problem with new multiple startupitems

2018-06-03 Thread Joshua Root
On 2018-6-4 00:31 , macpo...@parvis.nl wrote: > >> On 2018-06-03, at 16:05, Joshua Root wrote: >> >> On 2018-6-3 23:53 , macpo...@parvis.nl wrote: >>> startipitems \ >>> name testit \ >>> executable sudo -u paul /usr/local/bin/testit >> >> Should be: >> >> startupitems \ >> name testit \ >>

Re: problem with new multiple startupitems

2018-06-03 Thread macports
> On 2018-06-03, at 16:05, Joshua Root wrote: > > On 2018-6-3 23:53 , macpo...@parvis.nl wrote: >> startipitems \ >> name testit \ >> executable sudo -u paul /usr/local/bin/testit > > Should be: > > startupitems \ > name testit \ > executable "sudo -u paul /usr/local/bin/testit" > > Li

Re: problem with new multiple startupitems

2018-06-03 Thread Joshua Root
On 2018-6-3 23:53 , macpo...@parvis.nl wrote: > startipitems \ > name testit \ > executable sudo -u paul /usr/local/bin/testit Should be: startupitems \ name testit \ executable "sudo -u paul /usr/local/bin/testit" List elements are separated by whitespace, so if an element should con

problem with new multiple startupitems

2018-06-03 Thread macports
startipitems \ name testit \ executable sudo -u paul /usr/local/bin/testit gives this strange result: ProgramArguments /opt/port2/bin/daemondo --label=testit --start-cmd sudo ; --pid=exec where the old startupitem.executable sudo -u paul /usr/local/bin/testit gives this expec

Re: (Not) deprecating py35 subports

2018-06-03 Thread Rainer Müller
On 2018-06-03 01:37, Joshua Root wrote: > On 2018-6-3 07:28 , Mojca Miklavec wrote: >> The whole idea of the graveyard was to help users migrate to a newer >> version automatically, but in case of python it doesn't really serve >> the purpose if ports get moved to the graveyard at random times (ok,