Opened 8 years ago

Closed 8 years ago

#955 closed task (fixed)

Switch to Man-DB

Reported by: chris@… Owned by: William Harrington
Priority: minor Milestone: CLFS Standard 3.0
Component: BOOK Version: CLFS Standard GIT
Keywords: Cc: berzerkula@…, jonathan@…

Description

There hasn't been any new release of Man for several years, and the website has now been down for months. Because of this, we should probably switch to Man-DB, which is actually being maintained and has better i18n support and other features without the need for patches. This would require the addition of libpipeline, and either GDBM or Berkeley DB, to the book.

Change History (5)

comment:1 Changed 8 years ago by chris@…

I don't have any real preference for which DB we should use, but Man-DB itself prefers GDBM, so I think I'd just go with that. Both GDBM and libpipeline seem to have fairly minimal dependencies, not really anything beyond the usual Glibc/GCC/Binutils/Coreutils/Make/etc. that most other packages need anyway, so it shouldn't matter much where they are in the build order. Perl can use GDBM though, so GDBM can just be built before Perl, and libpipeline can be inserted alphabetically, right after Kbd.

comment:2 Changed 8 years ago by William Harrington

Milestone: CLFS Standard 3.0
Owner: changed from clfs-commits@… to William Harrington

I'm going to start adding this immediately.

GDBM I plan on installing right before Perl. Libpipeline and Man-DB after KBD.

Then remove man-1.6 from the book.

comment:3 Changed 8 years ago by William Harrington

I have added Man-DB, and with Chris's help, we have it pretty well situated in the book, now. I'll leave this ticket open throughout the weekend for testing, and if any problems arise, any devs with access to trac can post here. Users reading this ticket without trac access can post to clfs-dev mailing list.

comment:4 Changed 8 years ago by William Harrington

All is good. Closing ticket.

comment:5 Changed 8 years ago by William Harrington

Resolution: fixed
Status: newclosed
Version 0, edited 8 years ago by William Harrington (next)
Note: See TracTickets for help on using tickets.