Ruby ... active user sought

Bjarne D Mathiesen macintosh at mathiesen.info
Wed May 30 07:39:13 PDT 2012


Brandon Allbery wrote:
> On Wed, May 30, 2012 at 10:03 AM, Bjarne D Mathiesen
> <macintosh at mathiesen.info <mailto:macintosh at mathiesen.info>> wrote:
> 
>     Brandon Allbery wrote:
>     > On Wed, May 30, 2012 at 5:45 AM, Bjarne D Mathiesen
>     > <macintosh at mathiesen.info <mailto:macintosh at mathiesen.info>
>     <mailto:macintosh at mathiesen.info <mailto:macintosh at mathiesen.info>>>
>     wrote:
>     >
>     >     I've found this :
>     >     https://github.com/opscode-cookbooks/apache2
>     >
>     > I think you do not want to naively mix Chef and MacPorts, especially
>     > with a package that does not have any OS X support (much less
>     MacPorts).
> 
>     So ... you'ld recommend replicating it in tcl or bash ???
> 
> 
> I am not sure what you think you are trying to do.  But your message
> implied that you believe you've found some useful Ruby utilities.
> 
> You haven't.  They are Ruby, but they are plugins for a system
> management framework called Chef; they are not useful by themselves,
> only as components of that framework.  You can't use them at all without
> configuring a Chef installation; and it doesn't look like there's a lot
> of support for MacPorts so using it to manage anything installed by
> MacPorts may ultimately result in your needing to teach Chef how to deal
> with MacPorts as a package provider.
> 
> At least Chef supports OS X; I had thought it was still stuck in
> Linux-land.  But the Apache recipes you pointed to do not list OS X
> support at all, so your first hurdle would be porting those recipes to
> control MacPorts' Apache.  Their FreeBSD recipe might serve as a
> starting point — assuming there is some compatibility between their
> freebsd and macosx cookbooks.  (This is less about Ruby than it is about
> understanding how to maintain platforms and how to adapt between
> somewhat similar platforms.)
> 
> -- 
> brandon s allbery                                    
>  allbery.b at gmail.com <mailto:allbery.b at gmail.com>
> wandering unix systems administrator (available)     (412) 475-9364 vm/sms

We are having a discussion about replicating the Debian / Ubuntu layout
of the conf-files for Apache2 now that we are in the process of
upgrading the apache2 port to Apache httpd 2.4.x

So, I went hunting for a description of what Debian / Ubuntu does and
found those Chef recipes which looked somewhat promising - if not for
anything else, then as inspiration & documentation for our own work in
MacPorts

I had already entertained ideas of my own along the lines that the Chef
Apache2 CookBook uses, but I needed some hard information as to what is
actually done under Debian / Ubuntu as to file / directory structure and
utilites - and the cookbook has provided me with that insight :-)

Not knowing Ruby at all, I had no idea at all how I might possibly use
those Chef receipes, so I sougt out someone who could enlighten me :-)

And you've done so :-) for which I thank you :-)

Having seen your explanation, my conclusion has to be, that I'll have to
port those Chef receipes to use the macports framework and tcl.

:-) thanks :-)
-- 
Bjarne D Mathiesen
København N ; Danmark ; Europa
----------------------------------------------------------------------
denne besked er skrevet i et totalt M$-frit miljø
MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3


More information about the macports-dev mailing list