On Thu, Dec 01, 2011 at 08:41:12PM -0600, Brooks Davis wrote:
On Thu, Dec 01, 2011 at 05:55:37PM -0800, David O'Brien wrote:
On Tue, Nov 29, 2011 at 12:02:23PM +0700, Max Khon wrote:
It is possible to build and link our in-tree gdb friends with libedit
after r228114.
The remaining
David,
On Fri, Dec 2, 2011 at 3:17 PM, David O'Brien obr...@freebsd.org wrote:
Agreed and known. If the application(s) using libreadline weren't
already GPL I wouldn't have spoken up.
When I added the libreadline compatibility to libedit, I changed all the
non-GPL libreadline uses to
On Fri, Dec 02, 2011 at 12:57:20PM +0700, Max Khon wrote:
On Fri, Dec 2, 2011 at 8:55 AM, David O'Brien obr...@freebsd.org wrote:
If you go with (2) above, we'll still have *tons* of ports that want a
libreadline, so we'll just end up growing a port of it and we'll wind up
with a libreadline
David,
On Fri, Dec 2, 2011 at 3:43 PM, David O'Brien obr...@freebsd.org wrote:
On Fri, Dec 02, 2011 at 12:57:20PM +0700, Max Khon wrote:
On Fri, Dec 2, 2011 at 8:55 AM, David O'Brien obr...@freebsd.org
wrote:
If you go with (2) above, we'll still have *tons* of ports that want a
On Tue, Nov 29, 2011 at 04:46:30PM +0700, Max Khon wrote:
This is a separate issue that I want to handle separately.
I see no value in handling it separately. I either have a libreadline on
my system or I don't.
Again, what problem are you trying to solve?
The question is what to do with gdb
On Tue, Nov 29, 2011 at 12:02:23PM +0700, Max Khon wrote:
It is possible to build and link our in-tree gdb friends with libedit
after r228114.
The remaining question is what to do with libreadline:
1) just build link gdb with libedit
OR
2) re-import libreadline from gdb sources and build
On Thu, Dec 01, 2011 at 05:55:37PM -0800, David O'Brien wrote:
On Tue, Nov 29, 2011 at 12:02:23PM +0700, Max Khon wrote:
It is possible to build and link our in-tree gdb friends with libedit
after r228114.
The remaining question is what to do with libreadline:
1) just build link gdb
Brooks,
On Fri, Dec 2, 2011 at 9:41 AM, Brooks Davis bro...@freebsd.org wrote:
What is the value in doing either?
libreadline isn't infecting any non-GPL code turning into GPLv2.
Some of use have fancy .input files, and quite frankly the vi mode of
libedit still doesn't work quite the
David,
On Fri, Dec 2, 2011 at 8:59 AM, David O'Brien obr...@freebsd.org wrote:
This is a separate issue that I want to handle separately.
I see no value in handling it separately. I either have a libreadline on
my system or I don't.
What I meant is that this problem is not related to the
David,
On Fri, Dec 2, 2011 at 8:55 AM, David O'Brien obr...@freebsd.org wrote:
If you go with (2) above, we'll still have *tons* of ports that want a
libreadline, so we'll just end up growing a port of it and we'll wind up
with a libreadline on the system anyway.
Then you need to define what
On Tue, Nov 29, 2011 at 12:02:23PM +0700, Max Khon wrote:
Hello!
It is possible to build and link our in-tree gdb friends with libedit
after r228114.
The remaining question is what to do with libreadline:
1) just build link gdb with libedit
OR
2) re-import libreadline from gdb
Baptiste,
On Tue, Nov 29, 2011 at 3:59 PM, Baptiste Daroussin b...@freebsd.orgwrote:
It is possible to build and link our in-tree gdb friends with libedit
after r228114.
The remaining question is what to do with libreadline:
1) just build link gdb with libedit
OR
2)
On Tue, Nov 29, 2011 at 04:46:30PM +0700, Max Khon wrote:
Baptiste,
On Tue, Nov 29, 2011 at 3:59 PM, Baptiste Daroussin b...@freebsd.orgwrote:
It is possible to build and link our in-tree gdb friends with libedit
after r228114.
The remaining question is what to do with
The only problem I see is from the ports lots of them relies on base
libreadline, so we need to first run an exp-run without libreadline, to
determine the impact and fix the related ports, before we can fully drop
libreadline.
One of the first port to consider, i think, is rlwrap. Some time
14 matches
Mail list logo
