I think it's pretty clear that boost belongs in the C++ ground, so we shall move it to dev-cpp/.
Too much work for such, i'd said cosmetic change. We can not move package with vast amount of deps just in place. And using approach like was with python-exec can trigger some hard to catch bugs. So, i prefer to stay with current state. Other members of C++ Team keep silence, so, it seems that they are fine with it too. Closing as WONTFIX
Err, I don't see what magic do you want to do. It would be a clean package move, with 'move' entry in updates and so on.
(In reply to Michał Górny from comment #2) > Err, I don't see what magic do you want to do. It would be a clean package > move, with 'move' entry in updates and so on. Too many consumers in main tree AND overlays. For main tree we HAVE to ask infra to stop rsync updates or we will deal with broken tree for some time. We did such thing for qt migration and have some minor negative feedback. Boost have much more consumers, breakages will be usual thing. Qt packages migrates into new category for ease of maintainance and structure. Boost would move from dev-libs to dev-cpp... Not a big deal IMO, as i said...
(In reply to Sergey Popov from comment #3) > (In reply to Michał Górny from comment #2) > > Err, I don't see what magic do you want to do. It would be a clean package > > move, with 'move' entry in updates and so on. > > Too many consumers in main tree AND overlays. For main tree we HAVE to ask > infra to stop rsync updates or we will deal with broken tree for some time. > We did such thing for qt migration and have some minor negative feedback. > > Boost have much more consumers, breakages will be usual thing. > > Qt packages migrates into new category for ease of maintainance and > structure. Boost would move from dev-libs to dev-cpp... Not a big deal IMO, > as i said... I second that.
