Well, I can patch through horn. I think the git projects need to be removed, e.g. Rhino.Dsl and binary dependencies added.
Also the old Rhino code tree is massive and could do with some pruning. The only ones I am interested in are Rhino.Commons and Rhino.Security. I am sure there are people out there who differ with this opinion. Cheers Paul Cowan Cutting-Edge Solutions (Scotland) http://thesoftwaresimpleton.blogspot.com/ 2009/10/26 Lorenzo Melato <[email protected]> > > Ciao Paul, > > Its clear that I have no choice... I think Rhino.Commons is great and > that I must fix it in order to use it with the last nh and castle... > but if you have already make the patch I think the best choice is to > change the rhino tools source directly, for two reasons: > > You know that I'm a big fan of horn, but in this case I think the > patch must be available also to the not-horn users; > Patching rhino commons is a signal that the project is alive and > supported by someone of the community. > > > > On 26 Ott, 11:22, Paul Cowan <[email protected]> wrote: > > That leaves you with the choice of fixing or do not use :-) > > > > I use Rhino.Commons and I am going to update the horn descriptor to build > > Rhino.Commons against the git Rhino.Dsl and the latest Nhibernate and > > Castle. > > > > I can patch through horn or maybe I can change the source direct if > nobody > > has any objections. > > > > I just do not think I can devote too much time to Rhino.Commons because > of > > horn though. > > > > Cheers > > > > Paul Cowan > > > > Cutting-Edge Solutions (Scotland) > > > > http://thesoftwaresimpleton.blogspot.com/ > > > > 2009/10/26 Lorenzo Melato <[email protected]> > > > > > > > > > I agree, but unfortunately is not applicable to all scenarios. > > > > > Lorenzo Melato > > >http://blogs.ynnova.it/lorenzomelato > > > > > On 26 Ott, 11:12, Ayende Rahien <[email protected]> wrote: > > > > The best solution is to substitute time with money. > > > > > > On Mon, Oct 26, 2009 at 11:29 AM, Lorenzo Melato > > > > <[email protected]>wrote: > > > > > > > Ok Ayende, > > > > > > > the message is clear :-) > > > > > The problem is that I have no much time and I'm not practical with > the > > > > > rhino tools codebase. > > > > > > > There is someone who has already solved the problem in the > community > > > > > and have produced the patch? > > > > > > > Thank you, > > > > > > > Lorenzo Melato > > > > >http://blogs.ynnova.it/lorenzomelato > > > > > > > On 25 Ott, 23:26, Ayende Rahien <[email protected]> wrote: > > > > > > fix the build? > > > > > > > > On Mon, Oct 26, 2009 at 12:12 AM, Lorenzo Melato > > > > > > <[email protected]>wrote: > > > > > > > > > Hello, > > > > > > > > > there's a way to build Rhino commons against NHibernate 2.1ga > and > > > the > > > > > > > Castle trunk? > > > > > > > > > I have try to check out the r2200 from the svn as suggested by > > > Ayende, > > > > > > > copy the new binaries in the rhino tools SharedLib folder and > > > rebuild > > > > > > > all, but the build fail. > > > > > > > > > Lorenzo Melato > > > > > > > http:\\blogs.ynnova.it/lorenzomelato > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
