> > > Hi folks, > > > > > > I like to try bleeding edge beta versions. But I hate that if I will > > > install for example the new firefox 2 beta via portage, it will > unmerge > > > the current stable version. I would prefer to have a stable version > for > > > daily work and the beta version for testing purposes at the same time > on > > > my system. Therefore I would propose to introduce a policy, which > forces > > > each ebuild with the suffix _alpha, _beta or _pre have to be slotable. > > > > > Not feasable. You have 2 possible ways of doing it though. one is to > > use a chroot to test these things, and the other is to take a quickpkg > > of the stable version and emerge -k when you're done testing the > > bleeding edge stuff. > > Is it possible to get Portage (or ebuild) to build a package for > installation into /opt? If not, how much work would that be? > > What would be great would be to have emerge --optinstall package, that > installs the package into /opt/$PV and doesn't create a vdb entry... > feasible?
That sounds good. I already thought about making overlays which installs the files into /opt or a new subdir of /usr (for Example /usr/bleeding_edge or so) for all the beta stuff I want to test. But a simple emerge option or a config file like /etc/portage/package.opt would be great. Regards Sebastian Noack -- gentoo-dev@gentoo.org mailing list
