| 1 |
On Mon, 2006-08-07 at 09:31 -0500, Mike Doty wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Noack, Sebastian wrote: |
| 6 |
> > Hi folks, |
| 7 |
> > |
| 8 |
> > I like to try bleeding edge beta versions. But I hate that if I will |
| 9 |
> > install for example the new firefox 2 beta via portage, it will unmerge |
| 10 |
> > the current stable version. I would prefer to have a stable version for |
| 11 |
> > daily work and the beta version for testing purposes at the same time on |
| 12 |
> > my system. Therefore I would propose to introduce a policy, which forces |
| 13 |
> > each ebuild with the suffix _alpha, _beta or _pre have to be slotable. |
| 14 |
> > |
| 15 |
> Not feasable. You have 2 possible ways of doing it though. one is to |
| 16 |
> use a chroot to test these things, and the other is to take a quickpkg |
| 17 |
> of the stable version and emerge -k when you're done testing the |
| 18 |
> bleeding edge stuff. |
| 19 |
|
| 20 |
Is it possible to get Portage (or ebuild) to build a package for |
| 21 |
installation into /opt? If not, how much work would that be? |
| 22 |
|
| 23 |
What would be great would be to have emerge --optinstall package, that |
| 24 |
installs the package into /opt/$PV and doesn't create a vdb entry... |
| 25 |
feasible? |
| 26 |
|
| 27 |
Ed |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives