| 1 |
> > > Hi folks, |
| 2 |
> > > |
| 3 |
> > > I like to try bleeding edge beta versions. But I hate that if I |
| 4 |
will |
| 5 |
> > > install for example the new firefox 2 beta via portage, it will |
| 6 |
> unmerge |
| 7 |
> > > the current stable version. I would prefer to have a stable |
| 8 |
version |
| 9 |
> for |
| 10 |
> > > daily work and the beta version for testing purposes at the same |
| 11 |
time |
| 12 |
> on |
| 13 |
> > > my system. Therefore I would propose to introduce a policy, which |
| 14 |
> forces |
| 15 |
> > > each ebuild with the suffix _alpha, _beta or _pre have to be |
| 16 |
slotable. |
| 17 |
> > > |
| 18 |
> > Not feasable. You have 2 possible ways of doing it though. one is |
| 19 |
to |
| 20 |
> > use a chroot to test these things, and the other is to take a |
| 21 |
quickpkg |
| 22 |
> > of the stable version and emerge -k when you're done testing the |
| 23 |
> > bleeding edge stuff. |
| 24 |
> |
| 25 |
> Is it possible to get Portage (or ebuild) to build a package for |
| 26 |
> installation into /opt? If not, how much work would that be? |
| 27 |
> |
| 28 |
> What would be great would be to have emerge --optinstall package, that |
| 29 |
> installs the package into /opt/$PV and doesn't create a vdb entry... |
| 30 |
> feasible? |
| 31 |
|
| 32 |
That sounds good. I already thought about making overlays which installs |
| 33 |
the files into /opt or a new subdir of /usr (for Example |
| 34 |
/usr/bleeding_edge or so) for all the beta stuff I want to test. But a |
| 35 |
simple emerge option or a config file like /etc/portage/package.opt |
| 36 |
would be great. |
| 37 |
|
| 38 |
Regards |
| 39 |
Sebastian Noack |
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-dev@g.o mailing list |
Archives