RFC: Reduce Build Complexity of .Net Runtimes #219
Conversation
|
@ForestEckhardt will this have any ramifications for the .NET Execute buildpack? The order groups will change in the language family as well right, where the new buildpack will go after .NET Publish? Are any of the |
|
@sophiewigmore I added something to the implementation section to outline requires changes that will happen. If you would like more detail just let me know and I will break it done further! |
|
Do we want to add the buildpack re-order to this RFC as well? (i.e run ASP.NET / Runtime installation after source code is compiled?) This is what's sketched out in my spike listed in the Prior Art. |
|
@fg-j I think I would like to do this as a smaller chuck of work that would make the re-ordering easier to do in the future. |
|
IMO it would be nice to combine all of these concerns into one RFC |
|
I have spent a little time looking at the re-architecture and I feel like I would just need to tack an additional RFC on to the end of this RFC that is contingent on this RFC passing. I am happy to do that but I think that the purposed re-architecture that @fg-j is purposing becomes a trivial RFC that can reference this RFC and the SDK RFC once they both pass. Please let me know you would like me know what y'all are feeling and I will go with the popular vote. |
|
+1 I'd like it all to happen in this RFC. Gives us an opportunity to evaluate if there are edge cases we're missing and how we could cover them. |
|
2022-07-26 Working Group notes: waiting for approvals |
Co-authored-by: Forest Eckhardt <feckhardt@pivotal.io>
|
@paketo-buildpacks/dotnet-core-maintainers Am I good to merge this and get cracking on implementation? |
|
2022-08-02 WG Notes: Ready to merge. |
Readable