[SOLVED] what if I blacklist boost-1.70.0 before an update on current?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
what if I blacklist boost-1.70.0 before an update on current?
boost-1.70.0 is causing issues with certain after market installs of apps.
I reinstalled slack current off and older current dvd iso using boost-1.69 so I could get back what I lost. If I was to try and blacklist boost so does not update. Would that potentiality mess up other apps within current keeping boost at 1.69?
for example this is using boost 1.7
Code:
Fri Apr 12 22:13:09 UTC 2019
a/gawk-5.0.0-i586-1.txz: Upgraded.
ap/pamixer-1.4-i586-2.txz: Rebuilt.
Recompiled against boost-1.70.0.
With this install I got back qbittorrent, but iTunes does not fully work.
I am not in a the mood to pull a trial and error to find out at the moment.
bIf I was to try and blacklist boost so does not update. Would that potentiality mess up other apps within current keeping boost at 1.69?
Yes, it would mess up all packages that have already been recompiled against the boost 1.70 release.
The smart thing to do would be to "installpkg" this new release of boost, so that the older library stays on your system, but the new one will be there too (and is the default one).
Then those applications that still use the older one can find it, but all recompiled ones can find the updated library too.
When finally all of the programs have been recompiled you don't need the older library anymore so you can then "removepkg" that old release of boost.
Yes, it would mess up all packages that have already been recompiled against the boost 1.70 release.
The smart thing to do would be to "installpkg" this new release of boost, so that the older library stays on your system, but the new one will be there too (and is the default one).
Then those applications that still use the older one can find it, but all recompiled ones can find the updated library too.
When finally all of the programs have been recompiled you don't need the older library anymore so you can then "removepkg" that old release of boost.
BW-userx You can have more than one boost. You just point the application to that boost. Been a while.
but I did that when I ran across so programs that ran on older boost versions. so I renamed it to boost-1.4.9 and had the apps look for that.
Boost is a real pain. Been dealing with this issue for 9 years now on another huge program. slowly moving parts of it away.
usr/lib/boost-1.4.9
/usr/include/boost-1.4.9
one more thing you may want to build boost static and then at linking time it uses the .a not the dot.so.
make sure your .a is executable.
removed my .so on my static builds and thats how the project goes links static.
now no more version issue.
BW-userx You can have more than one boost. You just point the application to that boost. Been a while.
but I did that when I ran across so programs that ran on older boost versions. so I renamed it to boost-1.4.9 and had the apps look for that.
Boost is a real pain. Been dealing with this issue for 9 years now on another huge program. slowly moving parts of it away.
usr/lib/boost-1.4.9
/usr/include/boost-1.4.9
one more thing you may want to build boost static and then at linking time it uses the .a not the dot.so.
make sure your .a is executable.
removed my .so on my static builds and thats how the project goes links static.
now no more version issue.
sounds like fun tweaking.
I installed that alien bob boost, blacklisted 'boost' am running upgrade, I didn't see anything with the word boost in it to be installed.
so after this I think it got a peck and hunt to see whats what, as for me qbittorrent is the only thing I noticed that failed due to the boost update, and look into what you just mentioned. thanks for your insight.
so install this
boost-compat-1.70-x86_64-1alien.txz
and hold back the upgraded boost 1.7 and keep 1.69 installed?
what is your method of operation on this?
No, I don't blacklist boost. AlienBob's LibreOffice 6.1.4, for example, is dependent on an older version of boost so I needed the boost-compat package.
Last edited by mats_b_tegner; 04-21-2019 at 06:35 PM.
No, I don't blacklist boost. AlienBob's LibreOffice 6.1.4, for example, is dependent on an older version of boost so I needed the boost-compact package.
I got that torrent package qbittorrent needs fixed and boot I just went ahead and let it replace the 1.69 and still got bobs boost mini pac or whatever he called it installed. I was just sitting here thinking about removing it to see what that does, as I have to rebuild ffmpeg4 and mpv some of the video players do not work. never noticed before, because never used others because I been using mpv.
gmplayer, xine isn't working. I am not going to loose sleep over it , It is just something I noticed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.