On Mon, Aug 18, 2014, at 11:31, Ondrej Zajicek wrote: > On Mon, Aug 18, 2014 at 10:58:13AM +0200, Ondřej Surý wrote: > > Hi Micah, > > > > why would we need to ship birdcl together with birdc in one package? > > That makes no sense since birdcl is just no-readline version of birdc. > > I think it makes sense. Generally birdc is more suited to interactive > usage, while birdcl is more suited to non-interactive usage (although > both could be used in the other way). > > If you use birdc non-interactively using pipes, it cannot be ruled out > that readline would somehow interfere undesirably with it in some > unexpected way.
We have many other examples when the CLI is compiled with readline and it doesn't interfere (there was a problem in libedit in the past when using CLI in non-interactive way, but it's gone...). > Another possible reason is that some third-party scripts (like looking > glass or scripting language bindings) use birdcl by default, so they > would have to be modified to use birdc in case that birdcl is not > available. This could be solved by a symlink reducing the binary with duplicate functionality. Ondrej -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
