Skip to content

Conversation

@mistydemeo
Copy link
Contributor

This contains two commits broken out from #469 so that we can ship them later: the documentation, and the user-facing init code. This can be merged later so that, if we decide to, we can ship unadvertised pkg support early and then make it officially supported later.

@mistydemeo mistydemeo requested a review from Gankra August 28, 2024 20:07
Base automatically changed from pkg to main September 3, 2024 19:22
@ashleygwilliams
Copy link
Member

is this something we can merge? i know the code signing part is still not possible, but is this?

@mistydemeo
Copy link
Contributor Author

I think so, yeah. Because of the init code, rebasing this is going to make the most sense after config 1.0 is merged.

@mistydemeo mistydemeo force-pushed the pkg-followups branch 2 times, most recently from 7511a70 to ba532e0 Compare January 10, 2025 23:29
@mistydemeo
Copy link
Contributor Author

This conflicts, very badly, with #1653 and so this shouldn't be merged until that PR is done. The init code here will have to be 100% rewritten in order to be usable. It follows the patterns of the surrounding code, so it should ideally be obvious how to rewrite it to work with the new config structure once the surrounding code has been rewritten and is merged.

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

Successfully merging this pull request may close these issues.

3 participants