upgrading aaa_elflibs, contradiction
I was wonder about the recommended procedure for upgrading aaa_elflibs. I haven't had any problems for over 18 months, but would like to get a final answer on this.
In the slack package description of aaa_elflibs: Quote:
So does this mean it is or isn't safe to simply use "upgradepkg" on aaa_elflibs? |
Disregard. I found the answer.
Slackware aaa_elflibs and aaa_base packages Quote:
|
I believe during slackware-current I did have to upgrade aaa_elflibs because something had changed in one of the other packages. I believe a library that was part of apache was added to aaa_elflibs and when I upgraded apache the library was missing. I believe it was libmm. If i remember correctly there was some issue with the version of libmm which caused apache not to load and I had to actually upgrade aaa_elflibs in order to get apache working correctly again. You might want to look into changelog and search for libmm. I'm not sure if its an issue now but when upgrading regularly to slackware-current it was a brief issue for me.
|
All times are GMT -5. The time now is 03:06 AM. |