On Sat, Feb 04, 2017 at 07:12:01AM +0100, Floyd Anderson wrote: > On Fri, 03 Feb 18:34:22 -0700 > the...@sys-concept.com wrote: > >I have an old version of asterisk-1.8.28.2 (it is no longer in portage). > >I want to keep this version, temporarily (till I have a chance to test a > >new one 11.25.1-ver. > > If you have the asterisk-ebuild (and all related files) still available, > you could try to migrate it to a local overlay [1][2]. Otherwise, tell > Portage you are handle this package yourself by adding it to: > /etc/portage/profile/package.provided > > This file can be used to hold a specific version — even the package is > no longer in tree. But notice, this isn’t the whole truth as mentioned > in [3]. Portage will not update listed packages unless another package > requires a newer version of it.
I don't think package.provided will help in this case. He needs to rebuild the package to get rid of the old library so he needs the old ebuild and mask newer versions. But linking against a new library version can also cause problems so he might as well update it. If you *must* keep this build try adding --exclude='net-misc/asterisk' to the emerge @preserved-rebuild command and the old libraries used by asterisk will be preserved until you get a chance to update it but all other packages will use the new versions. > > Give it a try and invoke: > emerge --pretend --verbose net-misc/asterisk > to ensure if it’ll work as expected. > > References: > [1] > <https://wiki.gentoo.org/wiki/Handbook:AMD64/Portage/CustomTree#Defining_a_custom_repository> > [2] <https://wiki.gentoo.org/wiki/Overlay/Local_overlay> > [3] <https://wiki.gentoo.org/wiki//etc/portage/profile/package.provided> > > -- > Best regards, > Floyd Anderson > > >
