Summary: | mono-1.0.ebuild needed for mono-debugger-0.9.ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Richardson <prichardson> |
Component: | New packages | Assignee: | dotnet project <dotnet> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | prichardson |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.mono-project.com/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | mono-1.0.ebuild enhanced to support mono-debugger-0.9.ebuild |
Description
Paul Richardson
2004-07-03 06:44:00 UTC
Created attachment 34708 [details]
mono-1.0.ebuild enhanced to support mono-debugger-0.9.ebuild
mono ebuild
I'm very hesitant to be randomly include headers in our packaging of mono that aren't intended to be used. As much as it sucks to unpack a whole mono tarball, i find this to be a much better alternative (lesser of two evils). As for the extra USE flags, i personally would like to say no too, if somebody is in need of the preview stuff, then they should be following mono development closely, and be installing by hand/from CVS. As for the sigaltstack, I've not looked into the details of it either, if you can give me a concrete reason this warrants YALUF (Yet Another Local Use Flag), then i'd consider adding it. Marking WONTFIX. The debugger is package.masked until a new release which hopefully won't be as buggy/broken. |