Re: [Monotone-devel] Promoting usher to become a standard utility
In message [EMAIL PROTECTED] on Mon, 24 Oct 2005 22:48:22 -0700, Nathaniel Smith [EMAIL PROTECTED] said: njs Another option would be to move it out tree entirely, as a njs separate add-on that implements the 'monotone usher interface' or njs something. Doesn't seem like anything that really gains a whole njs lot from shipping with monotone itself (except as sample code), njs since the user base for it is so special; and if it's turning njs into a full-fledged app, then maybe moving it out would give njs useful flexibility in terms of things like choosing an njs appropriate testing architecture... I would agree, except that there's a dependency on the supporting features in netsync, so it would probably be good to make sure that for any release, usher and monotone are in sync. Regarding how special the use base of usher is, I think that's a matter of opinion. I know a bunch of people who like the idea, and I'd like to hear the rest of the list express their opinion before we declare anyone special. njs (I swear, the grammar is viral. :-)) Heh :-) Cheers, Richard -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up. -- C.S. Lewis ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Promoting usher to become a standard utility
I vote for in tree, and part of standard releases. Serving multiple distinct projects a'la CVS from the same server comes up repeatedly on the mailing list as something people would like to do. If monotone's answer is to have a separate utility to do it (and I like what I've seen of usher so far too), then I think it should be as painless as possible to get going with it. Not, oh, yeah, go download this other package and... in the manual. best, -emile On Tue, 2005-10-25 at 12:13 +0200, Richard Levitte - VMS Whacker wrote: In message [EMAIL PROTECTED] on Mon, 24 Oct 2005 22:48:22 -0700, Nathaniel Smith [EMAIL PROTECTED] said: njs Another option would be to move it out tree entirely, as a njs separate add-on that implements the 'monotone usher interface' or njs something. Doesn't seem like anything that really gains a whole njs lot from shipping with monotone itself (except as sample code), njs since the user base for it is so special; and if it's turning njs into a full-fledged app, then maybe moving it out would give njs useful flexibility in terms of things like choosing an njs appropriate testing architecture... I would agree, except that there's a dependency on the supporting features in netsync, so it would probably be good to make sure that for any release, usher and monotone are in sync. Regarding how special the use base of usher is, I think that's a matter of opinion. I know a bunch of people who like the idea, and I'd like to hear the rest of the list express their opinion before we declare anyone special. njs (I swear, the grammar is viral. :-)) Heh :-) Cheers, Richard signature.asc Description: This is a digitally signed message part ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Promoting usher to become a standard utility
On Mon, 2005-10-24 at 00:00 +0200, Richard Levitte - VMS Whacker wrote: Hi, I've seen enough good things happening with usher that I'd like to promote it to become a standard utility. All that would require would be that it got moved out of the contrib directory, that a test was created for it and that Makefile.am had the following change: [...] Opinions? Timothy? Hmm... I like this idea. ;) ...but then, it's hard to test properly since that would require doing things like reloading the config file and rearranging the servers while there's a number of open connections (in particular, when I first put in config file reloading any connections after the reload would go to a new server object, and so a new server process, even if the old server (likely with the same db) was still running (from still having open connections), even on servers that hadn't been changed), which I think the current test framework is entirely too linear to handle easily. Tim ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Promoting usher to become a standard utility
On Tue, Oct 25, 2005 at 12:08:07AM -0500, Timothy Brownawell wrote: ...but then, it's hard to test properly since that would require doing things like reloading the config file and rearranging the servers while there's a number of open connections (in particular, when I first put in config file reloading any connections after the reload would go to a new server object, and so a new server process, even if the old server (likely with the same db) was still running (from still having open connections), even on servers that hadn't been changed), which I think the current test framework is entirely too linear to handle easily. Another option would be to move it out tree entirely, as a separate add-on that implements the 'monotone usher interface' or something. Doesn't seem like anything that really gains a whole lot from shipping with monotone itself (except as sample code), since the user base for it is so special; and if it's turning into a full-fledged app, then maybe moving it out would give useful flexibility in terms of things like choosing an appropriate testing architecture... (I swear, the grammar is viral. :-)) -- Nathaniel -- Details are all that matters; God dwells there, and you never get to see Him if you don't struggle to get them right. -- Stephen Jay Gould ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Promoting usher to become a standard utility
Hi, I've seen enough good things happening with usher that I'd like to promote it to become a standard utility. All that would require would be that it got moved out of the contrib directory, that a test was created for it and that Makefile.am had the following change: # # old_revision [be65869bb72f4e219484a86e1c4a8eb33598b943] # # patch Makefile.am # from [3dbc9762de07d32c70441ccfb482d0206231fcf9] #to [c535c54730c1030072e5a9fd4f40220220370c2a] # --- Makefile.am 3dbc9762de07d32c70441ccfb482d0206231fcf9 +++ Makefile.am c535c54730c1030072e5a9fd4f40220220370c2a @@ -212,11 +212,12 @@ # primaries -bin_PROGRAMS = monotone +bin_PROGRAMS = monotone usher check_PROGRAMS = unit_tests noinst_PROGRAMS = txt2c monotone_SOURCES = $(MOST_SOURCES) monotone.cc main.cc +usher_SOURCES = usher.cc unit_tests_SOURCES = $(MOST_SOURCES) unit_tests.cc crypto_tests.cc txt2c_SOURCES = txt2c.cc Opinions? Timothy? Cheers, Richard -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up. -- C.S. Lewis ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
