![]() |
Update to repositories
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 |
Re: Update to repositories
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.
|
Re: Update to repositories
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. |
Re: Update to repositories
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 |
Re: Update to repositories
Quote:
I still don't think you actually understand what's going on here. |
Re: Update to repositories
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 |
Re: Update to repositories
Quote:
Quote:
No, this idea doesn't make sense. |
Re: Update to repositories
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) |
Re: Update to repositories
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.
|
Re: Update to repositories
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 |
Re: Update to repositories
No, Diablo was a hard reflash-and-reinstall. From here on out, we get SSU, which is about what you're talking about of rolling updates. But there'll only be updates to fix or enhance the OS, not random third-party apps that are packaged wrong...
|
Re: Update to repositories
I might be misunderstanding you all.. but effectively what I see is another example of people thinking that additions to a platform have become the standard...
I flashed to diablo and everything that came pre-installed with my Diablo functioned perfectly.. that is all that I can request or ask from Nokia. Anything beyond that was added by me and I had to learn how to do it... This would be akin to someone being extremely nice and making an Easy Installer for KDE and then the user base screaming at Nokia for not keeping it automagically up-to-date... Instead of everyone realizing that loading KDE was a benefit to begin with..they take it for granted and get angy if something experimental crashes their system or doesn't function the way they want it. Anything in "Extras" would be considered, by me, to be exactly that.. extra.. if I want to install it I do so with the understanding that I might have to fix it if it breaks.. in order to install any extra packages on my diablo I add to go add that Diablo/chinook thing in the Application Manager.. a very minute task IMHO to getting access to 1000's of software. |
Re: Update to repositories
I think if that's all you expect from aq distro then you probably were content with Minesweeper and Notepad. The OS should be a launch pad for applications giving them resources as needed. Where would the NIT be without the Canola's and Numpty Physics? On the store shelves.
Agreed, one shouldn't expect miracles with all third party applications, but there was a lot of headaches at the launch of Diablo getting "mainstream apps working. Where was the update? Just re-read the Canola or most any other applications' thread the first week or so. It was a painful experience for a lot of people. A simple update could have fixed it. I'm still not sure what repositories I should (only) have now... Or whether I should change them next week or the week after or.... C |
Re: Update to repositories
No, a simple update couldn't have fixed it.
|
Re: Update to repositories
how are old apps not working in a new os nokia's fualt, even with ubuntu you have to recompile apps between certian kernal revisions, you just want it all done early. I think the whole problem is that there is no beta test for the OS releases, so when you get the OS is when the Canola guys get it too...
|
Re: Update to repositories
Yes, that was something of an issue here; it was timed poorly. But for Fremantle, developers will have access to (weekly? I think) builds, so not a problem next time.
|
Re: Update to repositories
Well, let's hope the future just gets better for all concerned as we all get used to the new way of doing things.
C |
Re: Update to repositories
so you blame microsoft for every adobe flash - quicktime - java - roxio - and all games updates ever released right?? it's only fair to hold the big os's to the same standard... cuz i'll tell you right now as an admin for an active directory of more than 3000 workstations... you don't get any of that crap through WSUS..none.
unreasonable standards are unreasonable... nokia is not responsible for fixing every third party app released. i agree with benson that the biggest problem ive seen is no lead time for third party dev's to fix bugs before they are public.... but not a ton can be done about that |
Re: Update to repositories
Since Diablo, some changes have been made in extras repository.
Now, all free application are uploaded by sources and compiled on the server. So when a new version of maemo will be out, 98% of the applications should be available as it could be recompiled directly. This wasn't the case in chinook and previous version. But the change must be made one day ... and the community choice the diablo release ... |
All times are GMT. The time now is 17:36. |
vBulletin® Version 3.8.8