From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] skype package changes I don't understand
Date: Mon, 21 May 2012 10:54:08 -0700 [thread overview]
Message-ID: <CAK2H+efv0OKgSuBdgWwCN036-jBGd1KVjAWfNr+cPs9Lz192FQ@mail.gmail.com> (raw)
In-Reply-To: <4FBA77AA.6080307@gentoo.org>
On Mon, May 21, 2012 at 10:13 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
<SNIP>
>> if you use testing, you have to deal with such kind of situations.
>> Using a known broken version is just stupid. There isn't a choice
>> between those two. There is only a choice between: use unstable or
>> stable. And if you use unstable, don't complain about things being
>> fluid.
>>
Typical Volker. Not worth a response.
> - From what I can tell, he is not using ~amd64 (testing). He uses a
> mixed system (stable with a few packages in package.keywords) which
> sometimes is even worse :)
>
That's it precisely. All my systems are 'stable' as best they can be.
The only things that are more or less permanently testing are portage
& eix. After that the only entries in package.keywords are specific
applications or _very_ targeted things that address hardware issues.
(Virtualbox, VMWare Player, nvidia-drivers) That's it. In general, the
only reason ANYTHING goes in package.keywords is to address a
temporary package problem, and typically they aren't there that long.
For instance, if say Virtualbox had a problem I might keyword it for a
month or two to get a new release that fixes the problem. After that
version goes stable I remove the keyword entry and am running the same
version I've been running. My keyword file is currently only about 12
lines.
In the case of skype there was no stable version to use. Everything is
marked as testing.
While I agree that the emulation libraries are probably low risk I
don't want to add 8 new things to package.keywords. It's just not the
way I work here.
> The best way to deal with your problem (and avoid seeing your
> package.keywords getting bigger and bigger) is to grab -r1, mark it
> stable, put it in your local overlay and keep using that indefinitely.
>
Yeah, most likely the best medium-term solution although what I've
done for now is emerge -C skype.
> - --
> Regards,
> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Thanks Markos! I really appreciate your inputs as well as all the work
you guys do. We don't say thanks enough.
(Ugh Volker. Keep the attitude to yourself dude) ;-(
Cheers,
Mark
next prev parent reply other threads:[~2012-05-21 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 14:46 [gentoo-user] skype package changes I don't understand Mark Knecht
2012-05-21 15:04 ` Markos Chandras
2012-05-21 15:55 ` Mark Knecht
2012-05-21 16:09 ` Markos Chandras
2012-05-21 16:10 ` Volker Armin Hemmann
2012-05-21 17:13 ` Markos Chandras
2012-05-21 17:54 ` Mark Knecht [this message]
2012-05-21 18:15 ` Volker Armin Hemmann
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=CAK2H+efv0OKgSuBdgWwCN036-jBGd1KVjAWfNr+cPs9Lz192FQ@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@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