1,285
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + + + + + +
Features/Trigger Bundle Add (view source)
Revision as of 18:00, 21 October 2015
, 18:00, 21 October 2015no edit summary
== Summary ==
== Summary ==
There are many scripts that are external to the sugar shell that can install bundles, e.g, sugar-install-bundle, system package installer, and others. When these scripts are run and the sugar shell is running, the expected behavior would be see these installations reflected in the activity list, but it doesn't always happen.
There are many scripts that are external to the shell that can install bundles, e.g, sugar-install-bundle, system package installer, and others. When these scripts are run and the sugar shell is running, the expected behavior would be to see these actions reflected in the activity list, but it doesn't always happen. Often the activity list would:
* not show activities even though they are now installed, or;
* show the wrong version number for installed activities.
Restarting Sugar would fix the inconsistency.
After some research, we realized that there is a design flaw in the way the bundle registry detects these bundles. The registry uses GioFileMonitor to detect when new bundle directories are created, but, in many cases, it detects the creation before the contents of the directory are populated, so it can't find the activity.info file and the bundle gets ignored.
After some research, we realized that there is a design flaw in the way the bundle registry detects these bundles. The registry uses GioFileMonitor to detect when new bundle directories are created, but, in many cases, it detects the creation before the contents of the directory are populated, so it can't find the activity.info file and the bundle gets ignored.