Details
- Reviewers
- None
- Group Reviewers
Triage Team
Build libtorrent-raster against libboost 1.7.2
Build qbittorrent and run.
Diff Detail
- Repository
- R444 libboost
- Branch
- master
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
I'm not sure if I should bump every package using boost as I'm new to Solus environment.
Since the ABI version changed, every single package that uses libboost will need to be rebuilt against it and tested. However, we don't require a patch submission for a rebuild, only if something other than the release number must be changed for each package.
But before you go through all that effort, what is this even needed for? libboost upgrades are always painful and frequently require changes to the source of dependent projects or at least temporary patches to existing releases.
I would like to update libboost mostly because bug fixes, but I didn't know libboost upgrades are always painful.
I will abandon this revision because It's probably requires to make changes to many packages such as libtorrent-rasterbar, qbittorrent, etc.. thus I'm leaving to the update to @JoshStrobl.