| Summary: | ncurses doesnt create softlinks to terminfo files | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sascha Silbe <sascha-gentoo-bugzilla> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | major | CC: | dmeyett, fnjordy, gentoo-bugger, martin.danjou14, paidhi |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | patch for sys-libs/ncurses/ncurses-5.3-r5.ebuild: append --symlinks to configure options | ||
|
Description
Sascha Silbe
2004-02-17 04:15:07 UTC
Appending "--enable-symlinks" to the configure run of ncurses fixes this problem. Created attachment 26037 [details, diff]
patch for sys-libs/ncurses/ncurses-5.3-r5.ebuild: append --symlinks to configure options
forwarding to base-system Any chance of getting my patch into the official Portage tree? I currently have to manually patch the Portage tree before using catalyst to create the stage tarballs. :( *** Bug 40625 has been marked as a duplicate of this bug. *** Is it possible for users to create their own stage tarball to fix this problem without having gentoo in the first place, and how? Thanks. A work around has been proposed on the gentoo install forum that can be done after untaring the stage. I post it here for reference: http://forums.gentoo.org/viewtopic.php?t=171095 I'm curious why such a simple problem and solution is taking so long to remedy. I create numerous liveCDs for automated/unnattended installs of gentoo and changing the ebuild to use softlinks instead of hardlinks before I take a fresh snapshot is very very irritating. Not everyone wants /etc and /usr on the same filesystem. Arrrr! This still be a problem in 2004.2. Arrrrrrr!!! Frankly, it takes a long time to remedy because base-system is overloaded and understaffed. Committed to CVS. *** Bug 61204 has been marked as a duplicate of this bug. *** Reopening this bug... ...and reassigning it to release as a test-request *** Bug 62648 has been marked as a duplicate of this bug. *** |