| 1 |
Michael Mol wrote: |
| 2 |
> Dale wrote: |
| 3 |
>> Michael Mol wrote: |
| 4 |
>>> On Fri, Dec 23, 2011 at 5:38 AM, Mick<michaelkintzios@×××××.com> wrote: |
| 5 |
>>>> You need portage-2.2 to be able to use sets. |
| 6 |
>>> Sadly, 2.1.10.11 is the latest marked stable for ~amd64. (Or was, last |
| 7 |
>>> time I synced.) |
| 8 |
>>> |
| 9 |
>>> It'll be nice when it's available, though. |
| 10 |
>>> |
| 11 |
>> |
| 12 |
>> I been using the unstable portage for a long time. Since I built this |
| 13 |
>> rig if I recall correctly. It works fine but it does get updated pretty |
| 14 |
>> regular. Zac is always adding some new frills and shiney things. ;-) I |
| 15 |
>> wouldn't blame you for staying stable but it works fine here on my amd64 |
| 16 |
>> and old x86 rig. |
| 17 |
> |
| 18 |
> Devs don't seem to like bug reports involving mixes of stable and |
| 19 |
> unstable. I was mildly scolded for filing a bug report against xemacs' |
| 20 |
> failing to build with libpng15, when xemacs was stable, and libpng15 |
| 21 |
> wasn't, yet. I'm trying to being slightly more conservative about what |
| 22 |
> I unmask. |
| 23 |
> |
| 24 |
> Between autounmask and specific desires to be on top of some packages, |
| 25 |
> it's not easy. For example, stable WINE hasn't built since February |
| 26 |
> 2011... ( https://bugs.gentoo.org/show_bug.cgi?id=354745 ) Anyone who |
| 27 |
> needs WINE for any reason needs to use their unstable 1.3.x tree. This |
| 28 |
> isn't expected to be fixed until this coming *March*, when ICU 49 goes |
| 29 |
> generally available. |
| 30 |
> |
| 31 |
> /rant |
| 32 |
> |
| 33 |
> |
| 34 |
|
| 35 |
|
| 36 |
I file bugs with the unstable portage and I don't think I've ever heard |
| 37 |
them complain about running unstable portage. That said, sometimes when |
| 38 |
you run some software unstable and some not, then you can run into |
| 39 |
issues. A while back I was trying to burn home DVDs. I run the latest |
| 40 |
KDE4 but not all the way up to 9999 but unstable still. I had to also |
| 41 |
install unstable for the packages that it depended on as well. Things |
| 42 |
like DeVeDe and Bombono would not work well with them being unstable and |
| 43 |
the things under the hood running stable. Things like this, you have to |
| 44 |
make choices and just sort of figure out my trial and error. If in |
| 45 |
doubt, ask here first to see if a bug should be posted or not. If |
| 46 |
others have ran into the same issue, then maybe it needs to be filed |
| 47 |
possibly upstream. |
| 48 |
|
| 49 |
Thing is, the latest portage seems to fix things more than it breaks. |
| 50 |
It handles updates a lot better. The downside, docs are not to up to |
| 51 |
date. Zac manages to stay ahead of the docs at times. I monitor -dev |
| 52 |
to sort of keep up. |
| 53 |
|
| 54 |
Maybe they will mark it stable soon and you can test out all the new stuff. |
| 55 |
|
| 56 |
Dale |
| 57 |
|
| 58 |
:-) :-) |
| 59 |
|
| 60 |
-- |
| 61 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
| 62 |
|
| 63 |
Miss the compile output? Hint: |
| 64 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives