From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Virtuals revisited (Round 3)
Date: Thu, 7 Apr 2005 15:26:32 +0100 [thread overview]
Message-ID: <20050407152632.013dc62d@snowdrop> (raw)
In-Reply-To: <200504072220.43924.jstubbs@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
On Thu, 7 Apr 2005 22:20:43 +0900 Jason Stubbs <jstubbs@gentoo.org>
wrote:
| Back in my quest to rid the tree of the evil virtuals and their plot
| to destroy my mind. I think I've covered all bases with this one -
| perhaps even enough to satisfy TGL. Take your best shot!
1) You need an explicit example of what virtual/jdk/jdk-1.4.ebuild looks
like.
2) For the consistency section, I'm not sure how you're going to
implement this. The example I tend to use is this (versions simplified
slightly for clarity):
* User emerges vim-6.3, gvim-6.3. ~vim-core-6.3 is in as an RDEPEND.
* User upgrades to vim-7.0. ~vim-7.0 is in as an RDEPEND.
* User still has gvim-6.3 installed. gvim-6.3 has an RDEPEND upon
~vim-6.3, which is no longer installed. gvim is now broken.
An example of exactly how portage would 'solve' this would be
helpful. Would it ask for an unmerge of gvim-6.3 or would it include an
upgrade of gvim-6.3 as part of the "emerge ~vim-7"?
3) We don't specify every virtual in every profile thanks to cascades.
4) Backwards compatibility -- all virtuals ebuilds should include
DEPEND=">=portage-2.whatever" as well as the "|| ( foo bar )" stuff.
5) Someone tie up TGL and don't let him escape until he agrees to be a
dev this time.
--
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-07 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 13:20 [gentoo-dev] Virtuals revisited (Round 3) Jason Stubbs
2005-04-07 14:26 ` Ciaran McCreesh [this message]
2005-04-07 14:53 ` Jason Stubbs
2005-04-07 15:05 ` Ciaran McCreesh
2005-04-07 15:17 ` Jason Stubbs
2005-04-07 15:24 ` Ciaran McCreesh
2005-04-07 15:38 ` Jason Stubbs
2005-04-07 15:53 ` Jason Stubbs
2005-04-08 10:48 ` Paul de Vrieze
2005-04-09 4:07 ` Jason Stubbs
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=20050407152632.013dc62d@snowdrop \
--to=ciaranm@gentoo.org \
--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