Hello there, dev-libs/quantlib introduced a dependency on dev-libs/boost and I was forced to drop keywords on alpha, hppa and mips. I would like to know if boost can be keyworded if it works in those arches. Thanks
boost should work on any system with a sane toolchain, hoping to hear from the arch teams on this
Both of them re-keyworded ~alpha Cheers, Ferdy
Speaking of which, can we start keywording 1.32.0-r* stable? I'll verify on amd64 and x86.
Speaking of which, too, we are interested in having boost-1.32 marked stable to mark KDE 3.4 stable, do you think it can happen soon? Setting a blocker on bug 94223.
i see no reason not to keyword it stable this is actually me looking through the open boost bugs to determine if there is anything but feature requests even one bug requesting bjam to be installed is more of a feature request, i will finish checking bugs then marking stable
ok, don't hold your breath, one of the deps icc, aparently wont see a stable ic8.x and they will wait and push icc9 so no stable kde 3.4.x too soon if you need boost 1.32.0 , the other two deps should be able to be stabelized with some polite poking of g2boojum maybe just fyi
Daniel, Maybe a separate ebuild without an icc USE flag can be stabilized in the meanwhile?
Added ~mips.
Any news wrt comments #6 and #7?
any news with respect to #6, #7 and #9?
the latest news is that i don't even know if there will be a stable icc9 or not, worst case USE=icc would have to be deprecated then
icc support deprecated, now ebuild can go through usual process for stabelization
using this existing bug to ask the archs to stable 1.33.0-r1 instead of creating a new one
sparc boosted!
Removing hppa as keywording appears to be fine and has been for a while. Feel free to re-CC if this change seems inappropriate.
correct me if i'm wrong, but this should be taken care of
As far as I am concerned, it is. :-)