public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: foser <foser@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Using stow inside portage
Date: Sun, 18 Jul 2004 20:22:36 +0200	[thread overview]
Message-ID: <1090174956.9490.12.camel@rivendell> (raw)
In-Reply-To: <20040718105018.A26139@netdirect.ca>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

On Sun, 2004-07-18 at 10:50 -0400, Chris Frey wrote:
> > Isn't that the purpose of SLOTs?
> 
> Yes, and that's how some of the gcc's are done.  Unfortunately, slots seem
> to require developer resources to make work, and therefore aren't done
> on a consistent basis.  I.e. not all of the gcc's are slot-enabled, let
> alone KDE or Gnome or mozilla, etc.

Well, that's not really the purpose, SLOTs were meant to install
packages that are _upstream_ parallel installable. Afaik SLOTting in
Gentoo is consistent with most upstream releases.

You can redefine SLOT to do stow like stuff (afaik KDE in Gentoo does
this with different qt minor versions (?) & gcc), but I'm actually not a
big fan of that sort of constructions that do not comply with upstream
intent for no-good reasons : it's just great to have every mozilla
release on your system at the same time, but it serves no purpose (to
get back to your example). Adding global support for this will probably
lead to weird problems concerning libversion mismatching etc. .

- foser

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-18 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18  6:23 [gentoo-dev] Using stow inside portage Chris Frey
2004-07-18  6:28 ` Mike Frysinger
2004-07-18  7:14 ` Andrew Ross
2004-07-18 14:50   ` [gentoo-dev] " Chris Frey
2004-07-18 18:22     ` foser [this message]
2004-07-18 20:32       ` Chris Frey
2004-07-18 20:47       ` Martin Schlemmer

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=1090174956.9490.12.camel@rivendell \
    --to=foser@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