Summary: | Upgrade: ncurses-5.3.0.ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rigo <rigo> |
Component: | New packages | Assignee: | Nick Hadaway <grandmasterlinux> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | azarah, fluxbox |
Priority: | High | ||
Version: | 1.4_rc1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ncurses-5.3.0.ebuild |
Description
Rigo
2002-10-17 06:34:19 UTC
Created attachment 4778 [details]
ncurses-5.3.0.ebuild
I have added ncurses-5.3 to portage. It is currently masked. Please test and let me know if you experience any problems or any successes for that matter :) For any devs that poke into this bug, lets make sure to test it from a fresh build as well. Doesn't like -j8 on uniproc. Wont argue there, but otherwise it looks fine. *** Bug 9395 has been marked as a duplicate of this bug. *** Works fine for me. Probably worth looking into the threads on the forums about downgrading from 5.3 to 5.2 causing worlds of trouble, if that hasn't already been done, though. Bug 9517, if you prefer not to leave Bugzilla - sorry for the extra message. When would be the proper time to unmask ncurses-5.3? Should the ebuild be updated to depend on >=sys-apps/portage-2.0.43 so library symlinks get created correctly? I would say unmask, and then put ~ in KEYWORDS. The portage dep sounds fine. ncurses has been unmasked and marked unstable I have heard lots of good reports with the new ncurses... how long before we should mark stable? ncurses-5.3 is currently marked stable |