--
You received this message because you are subscribed to the Google Groups "HORN Development" group.
To post to this group, send email to horn-dev...@googlegroups.com.
To unsubscribe from this group, send email to horn-developme...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/horn-development?hl=en.
I haven't looked at Windsor yet, but I will probably look into it
eventually if someone else doesn't beat me to it.
-Michael Maddox
http://www.capprime.com/software_development_weblog/
--
You received this message because you are subscribed to the Google Groups "HORN Development" group.
To post to this group, send email to horn-dev...@googlegroups.com.
To unsubscribe from this group, send email to horn-developme...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/horn-development?hl=en.
mode debug:switches:parameters "project.config=debug", "sign=true","common.testrunner.enabled=false", "common.silverlight=false"I think we need to add a .NET 4.0 mode and then get this called from the windows service that builds the downloadable packages for the hornget website. I tried to install .NET 4.0 on the webserver last night but got a generic trust failure or some such error. I'll try again tonight.
S
> >>>>>>> <horn-dev...@googlegroups.com>horn-development@googlegrou
> >>>>>>> ps.com
> >>>>>>> .
> >>>>>>> To unsubscribe from this group, send email to
> >>>>>>> <horn-development%2Bunsu...@googlegroups.com>
> >>>>>>> horn-developme...@googlegroups.com.
> >>>>>>> For more options, visit this group at
> >>>>>>><http://groups.google.com/group/horn-development?hl=en>
> >>>>>>>http://groups.google.com/group/horn-development?hl=en.
>
> >>>>>> --
> >>>>>> You received this message because you are subscribed to the
> >>>>>> Google Groups "HORN Development" group.
> >>>>>> To post to this group, send email to
> >>>>>> horn-dev...@googlegroups.com.
> >>>>>> To unsubscribe from this group, send email to
> >>>>>> horn-developme...@googlegroups.com.
> >>>>>> For more options, visit this group at
> >>>>>>http://groups.google.com/group/horn-development?hl=en.
>
> >>>>>> --
> >>>>>> You received this message because you are subscribed to the
> >>>>>> Google Groups "HORN Development" group.
> >>>>>> To post to this group, send email to
> >>>>>> horn-dev...@googlegroups.com.
> >>>>>> To unsubscribe from this group, send email to
> >>>>>> horn-developme...@googlegroups.com<horn-development%
> >>>>>> horn-developmen...@googlegroups.com>
> >>>>>> .
> >>>>>> For more options, visit this group at
> >>>>>>http://groups.google.com/group/horn-development?hl=en.
>
> >>>>> --
> >>>>> You received this message because you are subscribed to the
> >>>>> Google Groups "HORN Development" group.
> >>>>> To post to this group, send email to
> >>>>> horn-dev...@googlegroups.com .
> >>>>> To unsubscribe from this group, send email to
> >>>>> horn-developme...@googlegroups.com<horn-development%2
> >>>>> horn-developme...@googlegroups.com>
> >>>>> .
> >>>>> For more options, visit this group at
> >>>>>http://groups.google.com/group/horn-development?hl=en.
>
> >>>> --
> >>>> You received this message because you are subscribed to the
> >>>> Google Groups "HORN Development" group.
> >>>> To post to this group, send email to horn-dev...@googlegroups.com.
> >>>> To unsubscribe from this group, send email to
> >>>> horn-developme...@googlegroups.com<horn-development%2B
> >>>> horn-developme...@googlegroups.com>
> >>>> .
> >>>> For more options, visit this group at
> >>>>http://groups.google.com/group/horn-development?hl=en.
>
> >>> --
> >>> You received this message because you are subscribed to the Google
> >>> Groups "HORN Development" group.
> >>> To post to this group, send email to horn-dev...@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> horn-developme...@googlegroups.com<horn-development%2Bu
> >>> horn-developm...@googlegroups.com>
> >>> .
> >>> For more options, visit this group at
> >>>http://groups.google.com/group/horn-development?hl=en.
>
> >> --
> >> You received this message because you are subscribed to the Google
> >> Groups "HORN Development" group.
> >> To post to this group, send email to horn-dev...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> horn-developme...@googlegroups.com<horn-development%2Bun
> >> horn-developm...@googlegroups.com>
> >> .
> >> For more options, visit this group at
> >>http://groups.google.com/group/horn-development?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "HORN Development" group.
> > To post to this group, send email to
>
> ...
>
> read more »
--
The similarity is that there is a dependency list between projects. The difference is that packages on which things depend are retrieved from package servers, and come in the form of compiled binaries. OpenWrap doesn’t compile *anything*, it just loads the right packages needed by other packages on local boxes.
Horn doesn’t retrieve packages, it retrieves source code to compile using a unified language to describe builds, which means it has to deal with a large amount of complexity and unreliability, and also meaning that everything gets recompiled everytime.
I’m not saying there aren’t areas in which the same problem exist, I’m saying that as openwrap doesn’t build anything, I’m not sure I’m comfortable with that idea that somehow I’m out to get horn, whatever I may be thinking of the project itself, its management or it’s applicability to what I’m trying to build.
Seb