| 1 |
I believe I have found an error in the way porthole is using portage. |
| 2 |
|
| 3 |
After an emerge sync which had a large number of update downloaded. I |
| 4 |
switched to our upgrades view which stated building the treeview. |
| 5 |
|
| 6 |
It was extremely slow, something I had noticed from time to time but did |
| 7 |
not know why. It usually finished before I determined why. This time |
| 8 |
using gnome system monitor I was able to determine that it was portage |
| 9 |
doing repeated calls to "ebuild.sh depend" for different packages. |
| 10 |
|
| 11 |
After it is complete a db reload and new upgrades list is quick again. |
| 12 |
|
| 13 |
Am I correct in that the imported instance of portage was still using |
| 14 |
the old metadata cache at the time of import? Even though the cache was |
| 15 |
updated at the end of the sync. After a sync we should re-initialize |
| 16 |
our instance of portage for it to use the new cache? |
| 17 |
-- |
| 18 |
Brian <dol-sen@×××××.net> |
| 19 |
|
| 20 |
-- |
| 21 |
gentoo-portage-dev@g.o mailing list |
Archives