Ebuild upgrade for cdw-0.5.0.ebuild and fix for cdw-9999.ebuild Reproducible: Always
Created attachment 239479 [details] New/Upgrade ebuild for cdw-0.5.0 New/Upgrade ebuild for cdw-0.5.0
Comment on attachment 239479 [details] New/Upgrade ebuild for cdw-0.5.0 Hang on, cleaning-up syntax. Will submitt 0.5.0 & 9999 ebuilds shortly.
Created attachment 239483 [details] Ebuild/Upgrade to cdw-0.5.0. Stable here on x86 and marking it as such. Should be stable on all other platforms. (cdw-0.4.0 had a serious configure file bug, fixed in 0.5.0!) Ebuild/Upgrade to cdw-0.5.0
Created attachment 239485 [details] I also cleaned-up both ebuild files so they look nicer. Added README and removed moved files for both ebuilds.
Eh. Seems I never had IUSE="debug" in the already in tree portage cdw-9999.ebuild -- it was only at my end here and the bug was non-existent within the portage ebuild. So it's an entirely new feature. For those of you using cdw, the debug USE Flag feature still pushes stderr to stdout corrupting the NCurses windows. So use something like "cdw 2>$HOME/.cdwdebug" to redirect stderr to a file. (I've already suggested doing something like Mutt and pushing stderr to file by default to the author/maintainer of CDW.)
HAI! Please file separate bug reports for separate issues next time. Oh, and don't CC maintainers when you cannot assign bugs...
Didn't realize media-optical email address was a private email address. (For the record, I did not enter your private email address -- Gentoo's Bugzilla configuration may have done this automatically.) Granted, usually would file separately, but they could also be considered extremely similar as they consist of same/similar syntax changes, aside from the fact one is an upgrade request.
version bumped in portage. I'm not really interested in the debug flag changes.
