Le 10/04/2012 13:27, [email protected] a écrit :
Hello
The XMLs are compatible. But there are some differencies in behaviour.
For example the commands in klish are non-interruptible by Ctrl^C by
default to make command execution atomic. The clish users can suppose
the commands are interruptible. And so on.
I think if someone really use clish it's not good to remove it
Serj Kalichev
On 10.04.2012 12:28, Viktar Palstsiuk wrote:
Hello Emmanuel
I'm not sure that clish and klish have 100% compatible XML configs.
So I think that klish can simply be added in the packages repository
without pushing out clish.
I'm fine with this. I'll let other (Viktar or anyone else) decide what
to do with clish.
Next message will contain a patch with a request to add klish to the
packages repository (this next message will not be CC'ed).
On Tue, Apr 10, 2012 at 10:47 AM, Emmanuel Deloget
<[email protected]> wrote:
(CC'ed to Vitkar and to the klish maintainer)
clish (Command Line Interface SHell) support has been added a few weeks ago
by Viktar [1]
and commited a few days later in the packages repository. I use clish, so
this is not a real
issue for me.
But clish is a seemingly dead project, with no update in the last two years
(approx.). It
has been forked at least onceand the fork seems to be a very active project
[2] (I found it
because I was about to create a similar fork on google code as well).
Thus the questions:
* does it make sense to keep clish in the packages repository?
* should we replace it with klish?
Best regards,
-- Emmanuel Deloget
[1]
https://lists.openwrt.org/pipermail/openwrt-devel/2012-February/014277.html
[2] http://code.google.com/p/klish/
Thanks everyone !
-- Emmanuel Deloget
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
