Some text doesn't respect Theme's font coloring.
1i5t5.duncan at cox.net
Mon Jul 11 21:54:49 BST 2011
Eric posted on Mon, 11 Jul 2011 13:42:21 -0400 as excerpted:
> Yeah Sabayon has been using the unstable branch of Gentoo for awhile,
> as well as changing the way USE flags, masked packages and one other key
> file (I think the file that lists all of your packages) are handled.
> They also used Baselayout 2.0, which is SOOOO Much nicer (along with
> Arch and i think FreeBSD) for awhile now. Last time I checked Gentoo
> still used the last 1.x of Baselayout.
Well, that's out of the way now, as gentoo stabilized baselayout-2/openrc
about a month ago. =:^)
> I asked on the gentoo forums and the sabayon forums what it would
> take to move from Sabayon to stock-Gentoo, figuring it would just take a
> remove of the Sabayon overlay and an emerge world, but the response on
> both sides said that with Sab on Baselayout 2.0 and the unstable branch,
> the changes in packages would probably be too far apart for it to be
> worth it. (Though, sidenote: Sabayon to Gentoo-unstable could be
> possible with a lot of tweaking.
Well, a lot of gentooers run ~arch by default, anyway. I know I do.
That's one of the reasons I push gentoo's customizability rather than its
freshness -- stale^h^hble isn't always so fresh, after all. Gentoo-
stable has the obvious problem for people who like current packages that
it does on any distro, except on gentoo the difference is even wider at
times, for factors somewhat unique to gentoo, including the fact that
~arch tends to run newer versions than many distros, while stable doesn't
necessarily have that distinction.
Before a new gcc is stabilized, for instance, it needs to be capable of
building the latest stable package of everything in-tree, which in
practice tends to mean a lot of corner-case-packages that few use and
that aren't well maintained upstream tend to need a stable-bump to build
with the new gcc first. That reflects the importance of gcc in a build-
from-source distro, but at the same time, means gcc takes a very long
time to stabilize -- disturbing given just that, its importance in a
And for the same root reasons, baselayout-2/openrc took "forever" to
stabilize. All system services needed all their openrc related bugs
fixed in one way or another first, and more than that, upgrade documents
had to be prepared. It didn't help that the original openrc upstream
author (with gentoo being "upstream" as openrc is a gentoo originated
project) got disenchanted and kind of left things where they were,
probably about 2/3 of the way thru the process, so it ended up just
sitting for a number of months until another gentoo dev volunteered to
> I'm actually looking at Arch again, spent a few hours last night
> re-roaming the wikis, looking up a few tips and tricks, and re-read the
> entire wireless and and wpa_supp articles over again, I think I actually
> found what I was doing wrong last time so I might give it another try
> when I get back home and I have a better (Faster) network connection
Someday I'll decide it's time, and will push to get wifi working on my
netbook... but meanwhile, using only the net only at home and only wired,
has been working well enough for the things I use the netbook for, as a
portable electronic bible and reference library (via the sword modules)
at church, etc, and as a portable media player with ~100 gig of space for
youtube videos, mp3s, etc. Neither really needs an active network
connection (since I don't run flash as it's servantware in the context of
my sig, youtube videos generally need downloaded to play in any case tho
at some point html5 will fix that), tho obviously, having one would be
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
More information about the kde