From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading to gcc 4.1 , question on recompiling
Date: Thu, 20 Jul 2006 09:02:19 +0100 [thread overview]
Message-ID: <20060720090219.5ead3154@hactar.digimed.co.uk> (raw)
In-Reply-To: <20060720000613.GA4807@sympatico.ca>
[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]
On Wed, 19 Jul 2006 20:06:13 -0400, Philip Webb wrote:
> > Running testing, most packages wb recompiled within a month anyway.
>
> I have a lot of "testing" packages, which run without problems.
That's different to running a completely testing system, the vast
majority of your packages are still stable and thus, by definition, won't
change very often.
> A lot of outstanding bugs seem to affect only a few special users.
> Yet again, Gentoo should make a 4th category by making "stable" =
> "server" & splitting "testing" into "newly unmasked" & "desktop-ready":
> many "testing" packages today are in fact desktop-ready,
> ie the remaining bugs will be rare & easy to recover from.
Remember that the distinction is not about bugs in the software but in
the ebuilds. I think the current system is fine with a choice of a low
maintenance system where working packages change rarely and one where you
have access to closer to the bleeding edge. If you want true bleeding
edge, you can always add packages to /etc/portage/package.mask. The
control /etc/portage gives you makes multiple levels of ARCH
unnecessary. You have already created your own set of "desktop-ready"
packages by customising package.keywords. Someone else may have
different requirements, let each user choose for themself.
> > I wanted to see if the 'kdehiddenvisibility' flag made any difference
>
> What was your experience ? Do you recommend others (me) to use it ?
I can't say I noticed a difference, but it mainly affects KDE startup
time and that's something I rarely do, and don't hang around to watch.
--
Neil Bothwick
No program done by a hacker will work unless he is on the system.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-20 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060719105701.59255.qmail@web61014.mail.yahoo.com>
2006-07-19 12:30 ` [gentoo-user] Upgrading to gcc 4.1 , question on recompiling Alexander Skwar
2006-07-19 13:05 ` Philip Webb
2006-07-19 13:20 ` [gentoo-user] " Sven Köhler
2006-07-19 13:34 ` [gentoo-user] " Alexander Skwar
2006-07-19 13:51 ` Richard Broersma Jr
2006-07-19 13:57 ` Alexander Skwar
2006-07-19 14:22 ` Neil Bothwick
2006-07-20 0:06 ` Philip Webb
2006-07-20 8:02 ` Neil Bothwick [this message]
2006-07-20 16:47 ` Alexander Skwar
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=20060720090219.5ead3154@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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