In message <[EMAIL PROTECTED]> on Tue, 30 Oct 2007 10:06:02 +0100, "Ralf S.
Engelschall" <[EMAIL PROTECTED]> said:
rse+monotone-devel> You mean, one file "xxx.lua" per command "mtn xxx"? Like
this:
rse+monotone-devel>
rse+monotone-devel> contrib/command/fuse.lua
rse+monotone-devel> contrib/command/conflicts.lua
rse+monotone-devel> contrib/command/foo.lua
rse+monotone-devel> contrib/command/bar.lua
rse+monotone-devel> contrib/command/quux.lua
rse+monotone-devel> ...
Yup, that's exactly the kind of thing I mean.
rse+monotone-devel> Sounds really reasonable to me, especially because
rse+monotone-devel> this way if one wishes to out-of-the-box include
rse+monotone-devel> some of the commands in an own Lua one just have
rse+monotone-devel> to add include("contrib/command/xxx.lua") to
rse+monotone-devel> std_hooks.lua and the stuff will be included
rse+monotone-devel> directly into the "mtn" command.
Not sure I'd do that. Read and heed the first few lines in
contrib/README. contrib/ is essentially unmaintained, except by the
contributors themselves. However, if we decide that some of the
commands are worthy enough to become part of the official package,
nothing stops us from moving them elsewhere (say, a lua-commands/ that
isn't under contrib/?) and have them actively maintained.
rse+monotone-devel> I vote +1 for Richard's suggestion and volunteer
rse+monotone-devel> to assemble the currently known commands there...
I'd say that there's nothing to stop you ;-)
Cheers,
Richard
-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
--
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
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
