Active Topics

 


Reply
Thread Tools
Posts: 74 | Thanked: 15 times | Joined on Feb 2008
#1
I keep reading about Diablo problems regarding repositories (Fring being the newest). We now have the ability to do a rolling update with Diablo, so why hasn't there been a fix to the repository problem. I hope ability to update isn't only being used just to install the next version version of the OS. Let's get this one working well...

C
 
Posts: 77 | Thanked: 9 times | Joined on Nov 2007
#2
I agree, the Fring fiasco has me wondering why we are trying to hack it to make it work when a simple update could fix it, like the authors of Advanced backlight app has taken advantage of, good work BTW. I'm also kind of wondering when the first Diablo update will showing up.
 
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#3
Uh, "repository probem"? What in the world are you talking about?

I think you guys have some sort of misunderstanding about how the whole system works, I'm just not sure what it is.

The Fring "fiasco" is entirely to blame on the idiots at Fring who don't know how to package a simple application.
 
Posts: 74 | Thanked: 15 times | Joined on Feb 2008
#4
I think you forgot about having to put extras/chinook in the repository listing. I use PCLinuxOS and it has a real rolling update where this kind of mistake is corrected easily and simply. I'm sure there are more than a few people that didn't have a pleasant first experience with Diablo - something that was so easy to fix.

C
 
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#5
Originally Posted by cybernut View Post
I think you forgot about having to put extras/chinook in the repository listing. I use PCLinuxOS and it has a real rolling update where this kind of mistake is corrected easily and simply. I'm sure there are more than a few people that didn't have a pleasant first experience with Diablo - something that was so easy to fix.
What does this have to do with SSU, though? Adding Chinook Extras to Diablo is an unsupported stop-gap solution until Diablo Extras gets fully up to speed.

I still don't think you actually understand what's going on here.
 
Posts: 74 | Thanked: 15 times | Joined on Feb 2008
#6
Maybe I don't understand but maybe there is a few more like me on this forum. I realize it's not rocket science to manually change the repositories, but I think it would be simple enough to do this for us "average" folks to make the first Diablo experience a little easier. If fring wasn't packaged correctly maybe Reggie shouldn't have promoted it quite so fast. Isn't that the reason for rolling updates? Maybe I've been spoiled by PCLOS - sometimes a little hand holding isn't a bad thing.
The keepers can always put the repositories back to "normal" when it is no longer a kluge - remember rolling update?

C
 
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#7
Originally Posted by cybernut View Post
Maybe I don't understand but maybe there is a few more like me on this forum. I realize it's not rocket science to manually change the repositories, but I think it would be simple enough to do this for us "average" folks to make the first Diablo experience a little easier. If fring wasn't packaged correctly maybe Reggie shouldn't have promoted it quite so fast. Isn't that the reason for rolling updates? Maybe I've been spoiled by PCLOS - sometimes a little hand holding isn't a bad thing.
No, he shouldn't have, but that's another issue. Fring installs the SDK repository on the device which should never be used on-device, as it can lead to reboot loops rather easily. It's a bad package.

Originally Posted by nilchak View Post
The keepers can always put the repositories back to "normal" when it is no longer a kluge - remember rolling update?
Nokia doesn't even ship the correct Extras enabled, why would you expect them to push an "update" to enable Extras for an old distribution?

No, this idea doesn't make sense.
 
Posts: 62 | Thanked: 3 times | Joined on Jul 2007
#8
I'm with you on this one, cybernut. Since nobody's responsible to give the nogo/go sign when something is supposed to work, it should be down somehow through the updates. Don't ask me how it all works. I just sit around and wait until others try it out and when it reaches a certain point I feel "safe", I close my eyes, plug my nose, and jump in.

The naming & renaming repositories...Shouldn't that be done upfront before an OS release? Or isn't backward-compatibilty guaranteed? (Really don't know)
 
ericdkirk's Avatar
Posts: 232 | Thanked: 45 times | Joined on Jul 2007 @ Tennessee, US
#9
I have to agree with the general, the software package you are talking about is the problem. You should always talk to more experienced people before installing new software. Ask yourself this, would you blame Apple if MS office crashed your mac, no you would blame the software installed, Nokia did not write this app, don't blame them.
 
Posts: 74 | Thanked: 15 times | Joined on Feb 2008
#10
Maybe I was mis-reading the forums. I thought a lot of people were initially having problems updating their applications - boy old age....
Maybe you don't realize what a rolling update should and/or does mean. Windows gives you an update when Bill decides (or used to) or Ubuntu when you reflash your system once every 6 months whether you want to or not (gee - I thought Diablo was taking us out of the dark ages...) or something with a rolling update -PCLOS for instance- where there can be daily (usually weekly) updates fixing peoples concerns. Isn't this what Diablo was supposed to do? Maybe I've been away from Windows too long and have enjoyed the other side. I guess we'll have to agree to disagree on this one - you'll never change my concept of rolling updates just like I'm not going to change yours. Have fun with windows waiting for SP4 - Oh I forgot - no more sevice packs...

C
 
Reply


 
Forum Jump


All times are GMT. The time now is 13:25.