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

Feature Request: add "extensible" tag to package-info.json #442

Open
rconstanzo opened this issue Feb 11, 2025 · 5 comments
Open

Feature Request: add "extensible" tag to package-info.json #442

rconstanzo opened this issue Feb 11, 2025 · 5 comments
Labels
enhancement New feature or request

Comments

@rconstanzo
Copy link

Is your feature request related to a problem? Please describe the problem.

As per the Max package doc "extensible" is:

An integer (0 or 1) to indicate whether this package can be extended by another package. Package extension means that the extending package becomes logically part of the extensible package in terms of how it appears in the File Browser and Reference Window. For instance, the RISE package extends the extensible BEAP package. As such, RISE patchers and documentation are included in the BEAP package entries in the File Browser and Reference.

As SP-Tools will eventually be on the Package Manager, and I'm using "extends" : "FluidCorpusManipulation",, it would be good if it tied in more directly.

Describe the solution you'd like to see.

Adding the following to package-info.json:
"extensible" : 1,

Describe alternatives you've considered

N/A

Additional context

I don't think this is the case already, but I imagine it would be possible/useful if someone installs SP-Tools, but does not have FluCoMa installed, that the combination of "extensible" and "extends" could make it such that the dependency (FluCoMa) is installed automatically(?).

@rconstanzo rconstanzo added the enhancement New feature or request label Feb 11, 2025
@tremblap
Copy link
Member

@jamesb93 do you foresee any issue? Otherwise it is trivial so I'll just PR it right away

@rconstanzo
Copy link
Author

Looking at the HIRT one, it has "extensible" : 0,, which I imagine is @AlexHarker being completionist in terms of filling in all the fields, but don't know what the implications are for having it set to "1".

@rconstanzo
Copy link
Author

I've inquired on the Max beta to see if there's any important implications/clarifications.

@rconstanzo
Copy link
Author

Ok, so right now you can only "extends" and "extensible" project. Nothing is done with dependencies one way or another, but nothing bad to happen with "extensible" being set to 1 (unless you specifically don't want it extended).

@jamesb93
Copy link
Member

Sorry I missed this. IIRC it's not a benefit or a badness either way as its unused. But it might get used in the future by the framework that deploys packages to users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants