From: _JusSx_ <jussx0@yahoo.it>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] QA issue: No stable skype in Tree
Date: Sun, 17 Jun 2007 16:06:32 +0200 [thread overview]
Message-ID: <20070617140632.GB7280@localhost.localdomain> (raw)
In-Reply-To: <46701D06.5080302@gentoo.org>
On Wed, Jun 13, 2007 at 05:36:22PM +0100, Gustavo Felisberto wrote:
> A little background info: Right now there are three versions of
> net-im/skype in the tree:
>
> 1 - the 1.2 series (with a stable version)
> 2- the 1.3 series also with a stable version
> 3- the 1.4 series with a ~/hardmask version
>
> Also the skype license states that we cannot mirror it's files (this
> will be need later)
>
> The 1.4 series will have a version released soon that skype wants to
> become the standard stable version, it has many new features and better
> audio quality.
>
> I as Gentoo Dev and Skype Betatester was informed that starting on June
> 19th Skype will no longer provide downloads for the 1.2 and 1.3 version,
> and that means that 1.4 will be released some time before. For Gentoo
> that means that starting from the 19th users on the stable profile will
> not be able to install skype as no files will be available from upstream.
>
> So the thing is, as soon as Skype releases the 1.4 stable version I'm
> going to have it in tree and we need to have it tested ASAP on the
> stable profile. My thing is with the time between, we will have 5 days
> tops or users will not be able to install.
>
> Suggestions:
> 1- in the 19th remove skype < 1.4 from the tree
> 2- Make < 1.4 ebuilds "empty" and leave them on the tree and ewarn the
> users to use the unstable skype
>
>
> The first option will trigger portage errors and prompt users to open
> bugs until we have a stable 1.4, the second gives us a chance to explain
> the issue.
>
> Any alternatives?
>
> --
> Gustavo Felisberto
> (HumpBack)
> Web: http://dev.gentoo.org/~humpback
> Blog: http://blog.felisberto.net/
> ------------
> It's most certainly GNU/Linux, not Linux. Read more at
> http://www.gnu.org/gnu/why-gnu-linux.html .
> -------------
>
>
Let's remove it from portage. why should we use it? I run it for a bit I
can say it's awful... it is closed-source, is not it? so I think it's
better not to install it...
--
Linux is only free if your time has no value
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-17 14:09 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 16:36 [gentoo-dev] QA issue: No stable skype in Tree Gustavo Felisberto
2007-06-13 16:41 ` Vlastimil Babka
2007-06-13 16:49 ` Steev Klimaszewski
2007-06-13 18:26 ` Petteri Räty
2007-06-13 19:44 ` Marijn Schouten (hkBst)
2007-06-13 19:58 ` Abhay Kedia
2007-06-13 20:12 ` Luca Barbato
2007-06-13 20:24 ` Vlastimil Babka
2007-06-13 20:36 ` Kent Fredric
2007-06-13 20:44 ` Vlastimil Babka
2007-06-13 22:23 ` Abhay Kedia
2007-06-14 7:01 ` Kent Fredric
2007-06-14 10:11 ` [gentoo-dev] Keeping closed source pkgs (Was: Re: QA issue: No stable skype in Tree) Steve Long
2007-06-14 11:11 ` Philip Webb
2007-06-14 14:48 ` [gentoo-dev] QA issue: No stable skype in Tree Luca Barbato
2007-06-14 15:11 ` Abhay Kedia
2007-06-14 21:45 ` Doug Goldstein
2007-06-15 4:31 ` Abhay Kedia
2007-06-15 11:15 ` Jan Kundrát
2007-06-15 13:03 ` Vlastimil Babka
2007-06-15 19:23 ` Richard Freeman
2007-06-17 19:05 ` [gentoo-dev] " Steve Long
2007-06-18 18:34 ` Chris Gianelloni
2007-06-19 2:32 ` [gentoo-dev] Determining ebuild stability and the 30 day suggestion (was: QA issue: No stable skype in Tree) Mart Raudsepp
2007-06-19 4:40 ` [gentoo-dev] Determining ebuild stability and the 30 day suggestion Luis Francisco Araujo
2007-06-19 21:05 ` Sune Kloppenborg Jeppesen
2007-06-19 22:33 ` [gentoo-dev] Determining ebuild stability and the 30 day suggestion (was: QA issue: No stable skype in Tree) Chris Gianelloni
2007-06-13 16:49 ` [gentoo-dev] QA issue: No stable skype in Tree Daniel Gryniewicz
2007-06-13 17:53 ` George Shapovalov
2007-06-13 18:28 ` Vlastimil Babka
2007-06-15 15:17 ` Jean-Marc Hengen
2007-06-15 13:45 ` Josh Sled
2007-06-17 14:06 ` _JusSx_ [this message]
2007-06-17 18:41 ` Josh Saddler
2007-06-17 19:08 ` [gentoo-dev] " Steve Long
2007-06-18 8:58 ` Duncan
2007-06-18 18:50 ` Chris Gianelloni
2007-06-18 20:25 ` Duncan
2007-06-17 19:10 ` [gentoo-dev] " Stephen Bennett
2007-06-18 5:01 ` [gentoo-dev] " Steve Long
2007-06-18 14:30 ` Steev Klimaszewski
2007-06-18 15:10 ` Steev Klimaszewski
2007-06-18 22:34 ` [gentoo-dev] " Steve Long
2007-06-18 18:39 ` [gentoo-dev] " Chris Gianelloni
2007-06-18 19:11 ` Wernfried Haas
2007-06-18 19:42 ` Daniel Ostrow
2007-06-18 22:49 ` [gentoo-dev] " Steve Long
2007-06-18 23:45 ` Chris Gianelloni
2007-06-19 1:54 ` Andrew Gaffney
2007-06-19 5:03 ` [gentoo-dev] Re: Pony Colour Schemes [was: QA issue: No stable skype in Tree] Ryan Hill
2007-06-19 6:14 ` Josh Saddler
2007-06-19 7:29 ` Kent Fredric
2007-06-19 21:07 ` [gentoo-dev] Re: Re: Re: QA issue: No stable skype in Tree Steve Long
2007-06-19 0:45 ` [gentoo-dev] " Seemant Kulleen
2007-06-19 5:31 ` Abhay Kedia
2007-06-19 7:25 ` Kent Fredric
2007-06-21 22:37 ` [gentoo-dev] " Vlastimil Babka
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=20070617140632.GB7280@localhost.localdomain \
--to=jussx0@yahoo.it \
--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