Multiple docset storages

[trollixx]

It might be convenient to have more than one docset storage.

Another use case would be a global docset storage (e.g. in /usr/local/share), and then allow users to have their own storage as well (~/.local/share).

Some primitive conflict resolution should work fine.

[rschwarzkopf]

In case you implement a global docset storage, I think it would be useful to allow the user to disable global docsets that are irrelevant for him. Otherwise, if a large number of global docsets is installed searching every search would need filtering - which is cumbersome if a search is supposed to be done in multiple docsets unless aliases ( #705 ) or Docset Groups ( #77 ) are implemented as well. But even with aliases and Docset Groups, disabling global docsets might be useful..

[tylla]

I totally support the idea. Something similar could be used under Windows as well.

Maybe a system/environmental variable (eg. ZEAL_DOCSET_PATH) could be consulted and the path therein used if it is defined. As about the conflict resolution, I would say the newer version for each docset should be used.

Our use case of this is a computer classroom where there are a few dozen shared computers and hundreds of users with each one possibly using Zeal and downloading one-two of the few most frequently used docsets. But multiplying the number of users with the number of machines and the number of docsets there is a huge wasted storage space which could be spared by putting the most used docsets in one central space (the variable could hold any path, even remote ones, that can be understood by the actually used OS). The extreme version of this case is where a computer room has to be prepared for an offline exam, where users are not allowed to download docsets - not even accessing the Internet - only to use the ones that are pre-downloaded for them. Currently this is a nightmare.