public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Edward Catmur <ed@catmur.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Beta versions should be slotable
Date: Mon, 07 Aug 2006 15:41:03 +0100	[thread overview]
Message-ID: <1154961663.20668.98.camel@capella.catmur.co.uk> (raw)
In-Reply-To: <44D74ED1.3090506@gentoo.org>

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



  reply	other threads:[~2006-08-07 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 13:29 [gentoo-dev] Beta versions should be slotable Noack, Sebastian
2006-08-07 14:00 ` Ciaran McCreesh
2006-08-07 14:31 ` Mike Doty
2006-08-07 14:41   ` Edward Catmur [this message]
2006-08-07 14:52     ` Andrew Gaffney
2006-08-07 16:11       ` Edward Catmur
2006-08-07 19:18 ` Enrico Weigelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1154961663.20668.98.camel@capella.catmur.co.uk \
    --to=ed@catmur.co.uk \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox