Michael Mol wrote:
Dale wrote:
Michael Mol wrote:
On Fri, Dec 23, 2011 at 5:38 AM, Mick<michaelkintz...@gmail.com> wrote:
You need portage-2.2 to be able to use sets.
Sadly, 2.1.10.11 is the latest marked stable for ~amd64. (Or was, last
time I synced.)

It'll be nice when it's available, though.


I been using the unstable portage for a long time. Since I built this
rig if I recall correctly. It works fine but it does get updated pretty
regular. Zac is always adding some new frills and shiney things. ;-) I
wouldn't blame you for staying stable but it works fine here on my amd64
and old x86 rig.

Devs don't seem to like bug reports involving mixes of stable and unstable. I was mildly scolded for filing a bug report against xemacs' failing to build with libpng15, when xemacs was stable, and libpng15 wasn't, yet. I'm trying to being slightly more conservative about what I unmask.

Between autounmask and specific desires to be on top of some packages, it's not easy. For example, stable WINE hasn't built since February 2011... ( https://bugs.gentoo.org/show_bug.cgi?id=354745 ) Anyone who needs WINE for any reason needs to use their unstable 1.3.x tree. This isn't expected to be fixed until this coming *March*, when ICU 49 goes generally available.

/rant




I file bugs with the unstable portage and I don't think I've ever heard them complain about running unstable portage. That said, sometimes when you run some software unstable and some not, then you can run into issues. A while back I was trying to burn home DVDs. I run the latest KDE4 but not all the way up to 9999 but unstable still. I had to also install unstable for the packages that it depended on as well. Things like DeVeDe and Bombono would not work well with them being unstable and the things under the hood running stable. Things like this, you have to make choices and just sort of figure out my trial and error. If in doubt, ask here first to see if a bug should be posted or not. If others have ran into the same issue, then maybe it needs to be filed possibly upstream.

Thing is, the latest portage seems to fix things more than it breaks. It handles updates a lot better. The downside, docs are not to up to date. Zac manages to stay ahead of the docs at times. I monitor -dev to sort of keep up.

Maybe they will mark it stable soon and you can test out all the new stuff.

Dale

:-)  :-)

--
I am only responsible for what I said ... Not for what you understood or how 
you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"


Reply via email to