Opened 19 years ago
Closed 19 years ago
#1727 closed defect (invalid)
Remove GDBM from BLFS
Reported by: | Randy McMurchy | Owned by: | Randy McMurchy |
---|---|---|---|
Priority: | high | Milestone: | 6.2.0 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
The GDBM package needs to be commented out of BLFS for the time being as it is now a part of Chapter 6 in LFS.
Change History (4)
comment:1 by , 19 years ago
Milestone: | future → 6.2 |
---|---|
Status: | new → assigned |
comment:2 by , 19 years ago
comment:3 by , 19 years ago
I haven't started yet, and will hold off until the UTF-8 is in place.
As far as folks using BLFS-SVN to build on top of LFS-6.1.1, this is not recommended, nor supported. BLFS-SVN target right now is LFS-SVN-trunk.
As far as I know, BLFS will not be releasing a 6.1.1 version (it has been discussed, whether discussion was on-line, I can't remember).
comment:4 by , 19 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
LFS moved to using BDB instead of GDBM for the DB backend. Marking this bug as invalid.
Note:
See TracTickets
for help on using tickets.
I don't know how soon you were planning on doing this, but I just reverted the UTF-8 patch to the LFS book as it's not quite ready. Also, it seems likely that many who build LFS-6.1.1 would use BLFS-svn instead of BLFS-6.1. Just food for thought.