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.

Sign up for GitHub

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

Jump to bottom

shade projects at the layer import level #1584

Open
propensive opened this issue Nov 24, 2020 · 0 comments
Open

shade projects at the layer import level #1584

propensive opened this issue Nov 24, 2020 · 0 comments
Assignees
@propensive
Labels
backend Relates to the backend data Relates to the format used for data storage enhancement New feature or request important Deserves high-priority attention
Milestone
Tisiphone

Comments

@propensive
Copy link
Owner

It seems like the best place to specify shading of a particular package would be at the layer import level. If you import a conflicting version of a particular project, you would potentially need to "rewire" an entire imported universe (i.e. from a layer) when you import that layer.
@propensive propensive added enhancement New feature or request important Deserves high-priority attention data Relates to the format used for data storage backend Relates to the backend labels Nov 24, 2020
@propensive propensive added this to the Tisiphone milestone Nov 24, 2020
@propensive propensive self-assigned this Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@propensive propensive

Labels
backend Relates to the backend data Relates to the format used for data storage enhancement New feature or request important Deserves high-priority attention
Projects
None yet
Milestone
Tisiphone
Development

No branches or pull requests
1 participant
@propensive