[gentoo-dev] Beta versions should be slotable

[gentoo-dev] Beta versions should be slotable

[Noack, Sebastian]

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.


Best Regards
Sebastian Noack

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Beta versions should be slotable

[Ciaran McCreesh]

On Mon, 7 Aug 2006 15:29:53 +0200 "Noack, Sebastian"
<S.Noack@AUTOonline.de> wrote:
| 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.

Too inflexible. Not all upstreams use sane versioning schemes. Now, if
we had slot deps, encouraging wider use of slots along with trivial
little eselect modules to handle the symlinks might be a good idea, but
requiring it is silly.

-- 
Ciaran McCreesh
Mail            : ciaran dot mccreesh at blueyonder.co.uk


-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Beta versions should be slotable

[Mike Doty]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Noack, Sebastian wrote:
> 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.
> 
> 
> Best Regards
> Sebastian Noack
> 
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.

- --
=======================================================
Mike Doty                      kingtaco -at- gentoo.org
Gentoo/AMD64 Strategic Lead
Gentoo Developer Relations
Gentoo Recruitment Lead
Gentoo Infrastructure
GPG: E1A5 1C9C 93FE F430 C1D6  F2AF 806B A2E4 19F4 AE05
=======================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iQCVAwUBRNdOzoBrouQZ9K4FAQLT+gP/Utlchg/9AG0UK1bGt9YLeDJex9p533Sp
emsRmBUDTr+r/iRLpIEoZDcfF/+kPAqQU/tFccaK/6aZdrayfi/DbOIn2wQ+/aAW
d82QND8c4wM5lQ8+oxkWU5oxJksIKpwLXh/R7qqSS2LUKXYYiBXEWR+kbdBNDnwS
l/5aNmApdCc=
=nP1h
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Beta versions should be slotable

[Edward Catmur]

On Mon, 2006-08-07 at 09:31 -0500, Mike Doty wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Noack, Sebastian wrote:
> > 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?

Ed

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Beta versions should be slotable

[Andrew Gaffney]

Edward Catmur wrote:
> 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?

Possible, sure:

emerge -B package
mkdir /opt/package
tar -C /opt/package -xjf /usr/portage/packages/All/package-ver.tar.bz2

Smart, not really. Using portage to install packages that are outside of 
portage's control is kinda silly. If you want to do that, build it by hand or 
use a pre-compiled package such as a RPM or DEB from the author's site.

-- 
Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer                                   Installer Project

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Beta versions should be slotable

[Edward Catmur]

On Mon, 2006-08-07 at 09:52 -0500, Andrew Gaffney wrote:
> Edward Catmur wrote:
> > 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?
> 
> Possible, sure:
> 
> emerge -B package
> mkdir /opt/package
> tar -C /opt/package -xjf /usr/portage/packages/All/package-ver.tar.bz2

Yeah, but the internals'd be screwy; hardcoded paths would point to
the /-based locations. Maybe (in effect) passing --prefix=/opt/$P to
configure?

> Smart, not really. Using portage to install packages that are outside of 
> portage's control is kinda silly. If you want to do that, build it by hand or 
> use a pre-compiled package such as a RPM or DEB from the author's site.

But using portage lets you use emerge's dependency resolution, build
system (ccache, distcc, etc), plus Gentoo patches and other fixes. With
a rpm or deb you don't have the faintest clue what you're getting...

Ed

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Beta versions should be slotable

[Enrico Weigelt]

* Noack, Sebastian <S.Noack@AUTOonline.de> schrieb:

<snip>

> 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.

Why not just putting alpha or beta packages in their own ebuild ?
ie. firefox-BETA ? 

Those ebuilds should live in their own testing overlay, to keep the
main tree smaller.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
-- 
gentoo-dev@gentoo.org mailing list