Reply
Thread Tools
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#11
Originally Posted by nicolai View Post
No.


How would you test an appication like blue sky theme, to work with
upcoming new versions of hildon-dekstop.
Blue Sky Theme is in maemos extras repository since last year.
Those changes to hildon-desktop are from this year,
and this hildon-desktop version is in extras-devel. And ifyou use new app versions
from extras-devel, you should now it can break things.
Testing is the reason why extras-devel and extras-testing are there.


Nicolai
When the hildon-desktop is re-written i think more the reason that apps should all be put through the testing stage again as it is obvious things are breaking, i personally think that for this community to be really sucessful, all and everything should be tested again and again for problems after any re-prog is done to make sure the OS is running smoothly and apps for all dependencies.

I think this is the main reason we have so many crashes going on so for this to stop i guess it must tighten it's belt a lot more and be more exacting in the development stages of Maemo.
 
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#12
Originally Posted by Switch_ View Post
Not forgetting reverting to standard hildon-desktop which would "break" certain parts of the CSSU

Code:
root
apt-get install --reinstall hildon-desktop
reboot
Yes and probably the main reason things are going wrong, what with the closed components and the huge job the CSSU is going through, this is making progress very slow indeed.

When Nokia designed the initial OS for the N900 the procedure i am sure would have been to make sure every single app was running without any crashes or conflicts.

I think it is so damm unfair of Nokia to pass on the future development of Maemo to this community knowing full well of the limitations they would face.
 
nicolai's Avatar
Posts: 1,637 | Thanked: 4,424 times | Joined on Apr 2009 @ Germany
#13
Originally Posted by abill_uk View Post
i personally think that for this community to be really sucessful, all and everything should be tested again and again for problems after any re-prog is done to make sure the OS is running smoothly and apps for all dependencies.
This is exactly what we are doing.
And the repository for new applications in development stage is
called extras-devel.
And the repository for new applications in testing stage is called
extras-testing.
Every new applications and every change in an existing applications
goes from extras-devel to extras-testing and only if
it is voted up by extras testers it will go to extras.
What do you think is missing in this procedure?

Nicolai
 

The Following User Says Thank You to nicolai For This Useful Post:
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#14
Originally Posted by nicolai View Post
This is exactly what we are doing.
And the repository for new applications in development stage is
called extras-devel.
And the repository for new applications in testing stage is called
extras-testing.
Every new applications and every change in an existing applications
goes from extras-devel to extras-testing and only if
it is voted up by extras testers it will go to extras.
What do you think is missing in this procedure?

Nicolai
This is a simple question to answer but has a huge impact on programming.

When any OS is in the making it goes through rigourus testing especially prior to public release, once it has "passed" with no conflicts should it be considered worthy of release.

OK we have now got a massive amount of apps on this community and there begins the problem with hildon, is it not possible for a main frame Linux computer to have every single app programmed and then checked over when hildon is re-written?.

One of the main and probably the biggest problem here is time, it is just taking too long for testing to happen to get out conflicts, and by the time we get anywhere Nokia will have brought out newer devices to make the N900 obsolete.

For Maemo to be successful Nokia has to give it in a complete open stage to the community board at least, to decide on further developments, this is simply has not done and the main reason the community can only go so far.

Hacking every component is possible but the legalities of that will prove to be a problem.

My honest opinion of all this is it is back to face and the coragous efforts of every single developer involved in this community is more or less working blindfolded because of Nokia.

My true opinions here would probably upset a few people so that is why i prefer to keep them to myself but for the hell of it i would attack Nokia direct if i had a full community behind me.

This is the way forward in my opinion Nicolai.

You are also a perfect example of a hard working developer that deserves much better support from Nokia as all developers need.
 
eefo's Avatar
Posts: 1,444 | Thanked: 461 times | Joined on Dec 2010 @ pakistan
#15
Originally Posted by Switch_ View Post
Not forgetting reverting to standard hildon-desktop which would "break" certain parts of the CSSU

Code:
root
apt-get install --reinstall hildon-desktop
reboot
this is what happened when i put this command
Attached Images
 
 
woody14619's Avatar
Posts: 1,455 | Thanked: 3,309 times | Joined on Dec 2009 @ Rochester, NY
#16
Originally Posted by abill_uk View Post
This is a typical example of an app that is allowed onto the download section of this forum that has not been tested 100% safe.
In fact, quite the opposite.

What has happened here is a package (blue sky theme) was selected, but the package says it's compatible with a desktop version up to 2.2.140. The error you got was that you have desktop version 2.2.142 installed, and so rather than install something that may break the desktop, it alerted you to this and prevented it from being installed.

This is not "broken". It's working as designed to protect you from installing something that may break things. This is how the package manager is supposed to work.

Yes, it would be great if all programs could magically be forward compatible with unseen changes, and all get re-tested and updated when new software comes out. But that takes time. If you want to test it, you can always force the package to install, test it's functionality, and report back to the author so they can update their dependencies if needed.

Please don't complain about things working the way they're supposed to!
 

The Following 2 Users Say Thank You to woody14619 For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 03:47.