Jouni Kosonen <jouni.kosonen <at> tukesoft.com> writes:
> Tanstaafl wrote: > > What I want is to be able to pin a specific package to the > > quickpkg'd > > version, so it doesn't get updated during an emerge world... > > Wouldn't it mostly work if you > a] Copied the package ebuild directory to a local overlay to ensure > the version keeps being available to portage even if it vanishes from > the official tree and > b] masked any later version in, say, /etc/portage/package.mask/pinned > ( and c] mentally prepared to repeat the procedure when the tree no > longer provides compatible dependencies ) Very similar to what I was musing/researching.... Some resources you may want to read up on that deal with slotting, and multislots (which allow for multiple versions (concurrent) installations for certain key packages. http://devmanual.gentoo.org/general-concepts/slotting/ euse -i multislot http://www.gnu.org/software/autoconf/autoconf.html A recent post on gentoo-dev "distutils-r1: set install paths via setup.cfg rather than argv" Just might provide you some ideas how to achieve what you want to do. I'm looking at a similar issue for my local overlays and codes I'm testing in a variety of forms; ebuilds and raw sources. hth, James
