public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eamon Caddigan <ecaddiga@uiuc.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Slotting Tcl/Tk
Date: Fri, 21 Nov 2003 14:40:01 +0000 (UTC)	[thread overview]
Message-ID: <slrnbrs8u1.e6l.ecaddiga@cancun.ks.uiuc.edu> (raw)
In-Reply-To: 20031121134441.GA31194@mail.ignum.cz

Stanislav Brabec <utx@gentoo.org> wrote:
> 
> Tcl/tk slots is bad idea. It can change only if somebody will hack all
> dev-lang/tcl (and some extra) ebuilds to be able to create simultaneously
> packages for both tcl/tk 8.3 and 8.4 (if they support building for both
> versions).

If this is true, then I feel it's imperative that Tcl/Tk 8.4 become
stable, and all other packages in portage are made to work with it. 8.4
is about a year old now, and I find it unacceptable that it's only
available as an "unstable" package. This situation reminds me of that
*other* distro.

I agree that there are a lot of potential issues involved with SLOTting
this package. Unfortunately, the only alternatives -- a similarly
massive effort to make sure everything works with the newest version, or
sticking with an increasingly out-of-date package -- seem worse.

Thoughts?

-Eamon


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-11-21 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  2:42 [gentoo-dev] Slotting Tcl/Tk Eamon Caddigan
2003-11-21 13:44 ` Stanislav Brabec
2003-11-21 14:04   ` [gentoo-dev] and Python! (Re: [gentoo-dev] Slotting Tcl/Tk) Jean Jordaan
2003-11-21 14:25   ` [gentoo-dev] Slotting Tcl/Tk Thomas de Grenier de Latour
2003-11-23 20:17     ` Stanislav Brabec
2003-11-23 23:40       ` [gentoo-dev] " Eamon Caddigan
2003-11-21 14:40   ` Eamon Caddigan [this message]
2003-11-21 14:54     ` Mike Frysinger

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=slrnbrs8u1.e6l.ecaddiga@cancun.ks.uiuc.edu \
    --to=ecaddiga@uiuc.edu \
    --cc=gentoo-dev@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