I emailed Daniel a few days back about submitting bugs to the tracker pertaining to Clang/LLVM support in Funtoo, and he wanted me to post in dev to let everyone know I'm probably going to be dropping quite a few bugs into the bugtracker. My previous ways to work around this were primarily based on my own personal system using the ebuild command, so branching them out to apply to the whole funtoo overlay is going to be an area I'm going to need some help with.
Just as an example, I just dropped a new bug in here http://bugs.funtoo.org/browse/FL-297
I'll always try to submit with some sort of workaround or patch vs a "it's broken" but there are probably going to be a few cases where I need an extra set of eyes if at all possible
Thanks for all the work you guys have put into funtoo, and I'm hoping eventually we can get most of the broken packages I've found ( https://github.com/pryoidain/pryoidain- … v/compiler ) to work out of the box
Sounds good - looking forward to more bug reports
Just out of curiosity, when I'm building the patches, should I attempt patching/test builds for all the packages in the tree? I was thinking I'll just do the most latest stable and most latest ~arch
testing all packages in tree is just an enormous amount of work, you can test a core packages, for example (content of stage3 packages), like you did for iproute2 and module-init-tools.