-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Managing Multiple StdLib Folders #9
Comments
Hmm, True. Good point, Ill post a commit on this soon. 🍔 |
Show this be a dropdown like the packsource option? |
Yes, as I said in the OP. |
Should installation have like a "checkbox" gui to have them installed in all/some dirs? |
No, it would just install the package to the StdLib folder you have currently selected. If you want to install it to another folder, you'd select said folder then install the package. The ASPDM client would grab the files then from the package cache. Same for uninstalling. I think you are going to need to implement some sort of reference counting for this. Oh, and still; the StdLib folder shouldn't be a global setting (even if it's a DDL); just a parameter that the ASPDM client temporarily uses, as if it were some sort of working directory. Some sort of metadata inside that folder will also need to exist in order to keep track of installed packages (which is not the same as packages inside the package cache). |
I'll be adding in this feature ("install from cache") soon, finally completing this enhancement. 😄 |
Currently it is not possible to manage several StdLib folders without having to change the settings.
Ideally the path to StdLib folder to manage should be a parameter to the package manager, not a global setting. Even more ideally so, there should be a dropdown in the interface that allows you to manage:
It would be possible to add previously-downloaded packages to these folders. Additionally, admin rights should not be required unless they are really needed: e.g. a temp file can be written to the folder in order to detect if they are needed.
The text was updated successfully, but these errors were encountered: