| 1 |
Alan McKinnon wrote: |
| 2 |
> On 03/08/2014 13:04, Dale wrote: |
| 3 |
>> |
| 4 |
>> |
| 5 |
>> True. I think the official claim is that once a year updates are |
| 6 |
>> supported. However, we have seen people that wait that long, and |
| 7 |
>> sometimes not even that long, and encounter a update process that deals |
| 8 |
>> with two or three deal breakers. I can't recall the package names but I |
| 9 |
>> know a couple packages can be a hair puller on their own. |
| 10 |
> icu, libxml, libpng and how can we forget |
| 11 |
> |
| 12 |
> <shudder> hal </shudder> |
| 13 |
> |
| 14 |
> and of course our recent friends python-exec as well as udev/upower-pm-utils |
| 15 |
|
| 16 |
Oh goodness, you wouldn't mention *THAT* one. :-@ lol Those are the |
| 17 |
ones I was thinking of tho. Those can be a bit tricky at best. At |
| 18 |
least they were before. It seems portage handles things better now but |
| 19 |
why ask for trouble? |
| 20 |
|
| 21 |
You know, hal is the only reason, other than smoke coming from a power |
| 22 |
supply, that I have ever had to actually pull the plug on a puter. |
| 23 |
Ever. Hitting the rest button, a couple times. Pulling the plug, not |
| 24 |
for anything outside that smoke issue. I cleaned the power supply with |
| 25 |
air and a rubber band was caught in the fan. It ran for a bit but got a |
| 26 |
little toasty at the end. ;-) It seems that fan runs for a good |
| 27 |
reason. :/ |
| 28 |
|
| 29 |
|
| 30 |
>> When you add |
| 31 |
>> in two of them at the same time, it gets bad really fast. So you make |
| 32 |
>> a good point. |
| 33 |
>> |
| 34 |
>> That is the reason I wanted to do updates about every week when I was on |
| 35 |
>> dial-up. I might would go two weeks at times. Now that I have DSL, I |
| 36 |
>> update usually twice a week. If I am expecting say a upgrade of KDE in |
| 37 |
>> between, I may add one that week or just shuffle my schedule to make it |
| 38 |
>> include the KDE upgrades. I have found that the twice a week updates |
| 39 |
>> are usually easier than the weekly ones when I was on dial-up. The |
| 40 |
>> improvements in portage could account for some of that but still, |
| 41 |
>> avoiding having two major changes at the same time is a good idea. The |
| 42 |
>> devs do seem to try and spread those apart a little anyway. They can't |
| 43 |
>> hold them forever tho. |
| 44 |
>> |
| 45 |
>> While every day may be a bit much, waiting months has its own issues. |
| 46 |
>> Then again, someone missing their WoW game may be a issue of its own. |
| 47 |
>> They may get . . . angry. LOL |
| 48 |
> I think the main problem with long gaps between updates isn't that stuff |
| 49 |
> breaks in new weird, wonderful ways never seen before (although that can |
| 50 |
> happen) |
| 51 |
> |
| 52 |
> The main problem is that you hit the same problems everyone else had and |
| 53 |
> solved months before and now can't remember what the solution was! Or |
| 54 |
> those who could help have forgotten about it, moved on and pay little |
| 55 |
> attention |
| 56 |
> |
| 57 |
> If you update weekly or bi-weekly on ~arch or monthly on arch you |
| 58 |
> probably hit issues at the tail end when problems are fresh in people;'s |
| 59 |
> minds and you can get first-rate help right here |
| 60 |
> |
| 61 |
|
| 62 |
That is a good point. At times when I see a upgrade issue mentioned |
| 63 |
here on the list, I wait a bit about my updates. Once things settle, |
| 64 |
bugs get worked out etc etc, then I upgrade mine with notes on how to |
| 65 |
fix a issue should it arise. |
| 66 |
|
| 67 |
Sometimes I wish folks could have a option for a third tier of the |
| 68 |
tree. One that is a month or so further behind for those that really |
| 69 |
need stable at all costs and minimal upgrade issues. Of course, that's |
| 70 |
not the Gentoo way tho. ;-) |
| 71 |
|
| 72 |
Dale |
| 73 |
|
| 74 |
:-) :-) |
Archives