Skip to content
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

IDB Goodies: Only package "IDB Method History" is loaded into default DPRO image #18

Closed
bernhardkohlhaas opened this issue Jan 6, 2016 · 5 comments

Comments

@bernhardkohlhaas
Copy link
Contributor

After building the most recent image with BootAll.cmd, I've noticed that the only IDB Goodies package that is installed into the DPRO image by default is the package "IDB Method History", even though I do see a lot more of the IDB Goodies under /Core/Contributions/IDB

Any reason, why those other Goodies are not installed into the image?

@objectarts
Copy link
Collaborator

Bernhard. My thoughts exactly, and you'll see I've just checked in a new master that loads the most important IDB tools (with some fixes to find resources etc). Note, that some of (what I consider to be) the less important packages are not loaded by default.

@bernhardkohlhaas
Copy link
Contributor Author

Nice, a lot more goodies now. :)

What I am wondering is, if the packages that aren't installed by default should go in to a separate directory structure, say "Optional". The reason I am saying this is that I didn't expect that there would be packages in the /Core directory structure that aren't installed into the image by default, when it is booted up.

I'm actually not not that a separate directory structure is the best solution, I am just wondering, what would be a good way to show folks that there are other packages coming with the project that are available, but have to be installed manually.

@objectarts
Copy link
Collaborator

The current scheme is:

  1. Use Core/Contributions for third party packages that are pre-loaded into the booted images. Either the authors wish that these packages be kept separate from the base or it makes more sense to do so because they are large blocks of functionality. Core/Contributions are still regarded as system packages and will be distributed inside all end-user images.

  2. Optional non-system packages are held in the separate Contributions repository and can be loaded on demand by the end-user.

I'll close this issue for now.

@bernhardkohlhaas
Copy link
Contributor Author

@objectarts : So that means the IDB packages that aren't loaded into the image by default need to be moved into the Contributions repository, correct?

@objectarts
Copy link
Collaborator

Yes, ideally.

blairmcg pushed a commit that referenced this issue Jun 14, 2018
Cleanup runtime error when assigning to a smaller container.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants