Change History (5)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
The instructions for how to build XFree will always be available in the BLFS museum. There's no need to keep it in BLFS svn
comment:3 by , 18 years ago
Sorry Andy, but I must disagree, citing points 1,2, and 3 above from Randy. 4 I'm not so sure about, but it's not relavent to this bug. I've not really cared about this one in the past, then a new release appeared. As I see it right now, there is no reason to remove XFree86. It's been updated to the latest version already, the instructions rarely change, and the maintainers are still present and active. If a new version comes out, or a major security flaw is discovered, *and* if no editors want to update it, then It can be removed at that time. But for now, I feel that it is a working package that shouldn't have much of a maintenance burden.
comment:4 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Although I agree that XFree is beyond its prime, I think we should keep it in the book for now. We have multiple editors, window managers, and even ghostscript apps. There is no reason to drop XFree right now.
I suspect most of the talent is now in Xorg and that XFree will be dropping behind technically. We do need to keep reviewing the topic as new releases of both Xorg and XFree are made.
Marking as wontfix, but we should review this topic again at the next major BLFS release after 6.2.
It is now more crucial than ever that XFree is kept in the book. Reason 4 below is why I say this.
maintained.
maintenance.
user base.
XFree would then be the choice for users who don't wish to go through the modular build hassle.