Thank you as always, Chet. Worked as announced ;). I've wrapped it up inside an Arch PKGBUILD and published it in the AUR [1]. I had to symlink 7 libs to 6 in order to keep the system working. At first sight I find no issues, but do you think is too rude even for a development "do it at your own risk" package? Are there severe binary incompatibilities?
Btw, the new mode-in-prompt indicators are cool, is the text configurable? Cheers -- Carlos [1] https://aur4.archlinux.org/packages/readline-devel-git/ On Mon, Aug 3, 2015 at 5:53 PM, Chet Ramey <[email protected]> wrote: > On 7/31/15 1:31 PM, Carlos Pita wrote: >>> didn't work was that the readline state machine was messed up. I will have >>> a fix in the next testing release of readline. >> >> In general, what's the best way to get, test and install development versions >> of bash/readline? >> >> I'm asking that because the commits and references in: >> >> http://git.savannah.gnu.org/cgit/readline.git/log/ >> http://git.savannah.gnu.org/cgit/readline.git/refs/ >> >> are 3 weeks old, so your fixes obviously aren't there. > > I just created a `devel' branch in the readline git repository on > savannah. You can get updated development snapshots there, just like > the bash `devel' branch. > >> Also, I'm not sure how much coupled the two projects are. Can I update >> readline while keeping the bash version?, etc. > > Yes, using the readline devel branch. Bash is where nearly all of the > readline development happens, but you will be able to build standalone > versions of readline using the devel tree. > > I haven't separated out the readline changelog entries from the bash > changelog (and may not get to doing so). > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, ITS, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/ _______________________________________________ Bug-readline mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-readline
