Community
Participate
Working Groups
There are a number of preferences which are used by elements of a p2 agent. Things like lists of repos, GC enablement, ... These are all managed using the global preference store. That is, the p2 code in an agent gets THE pref store and looks up/sets THE preference. That means that if you turn off GC for one agent, it is turned off for all. The agents should either use their own prefs service or allow for an agent specific pref path prefix to be supplied.
Since 3.6 we have an agent scope. It might be enough to change the code to use this instead. That said, if I remember correctly there is still one issue for some preferences since they are profile specific and at the point of the preference access the profile is not always known / accessible. For example this is the case for repos, the repo manager tries to make a best effort to save the list of repos in a profile specific manner.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the stalebug whiteboard tag.
