startupitem.inetdcompat or newbie base hacking!

James Berry jberry at
Sun Apr 22 16:32:47 PDT 2007

Hi Mark,

On Apr 22, 2007, at 1:50 PM, markd at wrote:

> James Berry <jberry at> on Saturday, April 21, 2007 at  
> 7:45 PM
> -0800 wrote:
>>> I think it would be desirable to have a startupitem that supports
>>> inetdcompatibility in MacPorts.  It seems to me it wouldn't be that
>>> hard
>>> since the heavy lifting was already done in MP 1.2.  So I've hacked
>>> the
>>> portstartupitem.tcl file for some new startupitems and I want to
>>> test it
>>> so I tried replacing the current copy in ${prefix} with the
>>> modified file
>>> but it isn't recognizing my new variables.  What is the proper way
>>> to test
>>> a new portstartupitem.tcl file?
>> Great idea to work on that stuff a bit more. Modifying the code in $
>> {prefix} is the right thing to do. I'm not sure which variables
>> you're having trouble with, but one thing to be aware of is that the
>> option variables for startupitem are declared in portdestroot.tcl.
> James,
> You were right, defining the new keywords in portdestroot.tcl made  
> them
> available.  They need some more review and attention but I've got  
> these
> new keywords working:
> startupitem.inetdcompat
> startupitem.inetdcompat.socketsvcname
> startupitem.inetdcompat.nowait
> They are attached to this ticket:

That looks pretty good. I'd love to hear feedback from others, but  
I'd favor commiting this to allow some experimental usage.

> How hard do you think it would be to support multiple  
> startupitems?  If
> I'm not mistaken only one is supported now.  I have ports that  
> could use
> more than one startup script.

I don't think that was really anticipated in the design; we've have  
to change the syntax somehow to allow multiple items.


More information about the macports-dev mailing list