![]() |
2010-06-01
, 09:02
|
Posts: 208 |
Thanked: 17 times |
Joined on Jan 2010
@ Belgium
|
#2
|
![]() |
2010-06-01
, 09:49
|
Posts: 148 |
Thanked: 31 times |
Joined on Mar 2010
|
#3
|
|
2010-06-01
, 10:15
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#4
|
![]() |
2010-06-01
, 10:21
|
Posts: 104 |
Thanked: 47 times |
Joined on Sep 2009
@ Kassel, Hesse, Germany
|
#5
|
![]() |
2010-06-01
, 10:26
|
|
Posts: 1,111 |
Thanked: 1,985 times |
Joined on Aug 2009
@ Åbo, Finland
|
#6
|
![]() |
2010-06-01
, 10:39
|
|
Posts: 290 |
Thanked: 165 times |
Joined on Sep 2009
|
#7
|
The problem lies in the way hildon-application-manager (ham) interacts with APT. Instead of utilizing the apt-pkg library, the ham launches a subprocess (apt-worker) to communicate with APT. This subprocess has to parse the sources list, read the cache, and communicate with ham via the standard file descriptors (stdout, stdin, stderr). That's mostly done for security purposes I guess, to not have ham run as root.
Fixing this does not look easy to me, and especially I would not consider Nokia to fix this for fremantle. It might require changes to the protocol used by apt-worker and could easily break things.
![]() |
2010-06-01
, 10:40
|
|
Posts: 1,111 |
Thanked: 1,985 times |
Joined on Aug 2009
@ Åbo, Finland
|
#8
|
ah so the thing is, can the community not create a nice ui over apt-pgk? that then has to run as root ofcourse but with much more speed?
![]() |
2010-06-01
, 11:04
|
|
Posts: 2,869 |
Thanked: 1,784 times |
Joined on Feb 2007
@ Po' Bo'. PA
|
#9
|
The problem lies in the way hildon-application-manager (ham) interacts with APT. Instead of utilizing the apt-pkg library, the ham launches a subprocess (apt-worker) to communicate with APT. This subprocess has to parse the sources list, read the cache, and communicate with ham via the standard file descriptors (stdout, stdin, stderr). That's mostly done for security purposes I guess, to not have ham run as root.
Fixing this does not look easy to me, and especially I would not consider Nokia to fix this for fremantle. It might require changes to the protocol used by apt-worker and could easily break things.
![]() |
2010-06-01
, 18:31
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#10
|
The problem lies in the way hildon-application-manager (ham) interacts with APT. Instead of utilizing the apt-pkg library, the ham launches a subprocess (apt-worker) to communicate with APT. This subprocess has to parse the sources list, read the cache, and communicate with ham via the standard file descriptors (stdout, stdin, stderr). That's mostly done for security purposes I guess, to not have ham run as root.
Fixing this does not look easy to me, and especially I would not consider Nokia to fix this for fremantle. It might require changes to the protocol used by apt-worker and could easily break things.
If i do apt-get update and apt-get upgrade i am done in no time.
But if i do what i see the same in the AppManager, yes also in the one from 1.2 that was reported as much faster... it is soo slow.. All things take for ever
Just starting it and i see my cpu spiking (apt-worker)
I guess this is opening the app manager now auto updates every time you start appmanager (why is this in 1.1.1 i had i think an option to say update now??)
But why does this take so much longer then doing it from the command line??
(and way way more cpu power, through the command line almost no cpu power is used, its more downloading)
And the same for updating, or if i downloaded an app then it is also crunching and crunching after every install.. Why??
For now i do all my updates through the xterminal and only touch appmanager when i really want do download something new.. But this should really be looked at in my point of view.