Skip to content

Plugin mechanism for virtual packages #10131

@jakirkham

Description

@jakirkham

Virtual packages have been popular since their introduction with __cuda ( #8267 ). Since then we have added __glibc ( #9358 ), __osx ( #9349 ), and are now looking at architecture specific ones ( #9930 ). As the use cases here expand, wonder if we should begin discussing a plugin architecture for the community to supply virtual packages and how these can be enabled and which ones we include by default. Thinking about this in the context of maintenance, extensibility, ease of use, etc. Thoughts? 🙂

Metadata

Metadata

Assignees

Labels

locked[bot] locked due to inactivitypluginspertains to a plugin/subcommandsource::communitycatch-all for issues filed by community memberstype::featurerequest for a new feature or capability

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions