example-custom-config-repo VS vendor_calyx

fork the example custom config repo: https://github.com/RattlesnakeOS/example-custom-config-repo

Thanks for the response! So in this new model, custom patches would be moved into the hook shell scripts and could be applied at various stages of the build process. The hook shell scripts that execute can really do whatever, but an example of installing a patch from the community patches can be seen here: https://github.com/RattlesnakeOS/example-custom-config-repo/blob/HEAD/hooks/aosp_build_pre.sh#L9. In this case the patches are applied prior to the AOSP build starting (aosp_build_pre). This could obviously be simplified a bit more, but this would be the current migration path.

I've been working on some rather large updates to rattlesnakeos-stack, as I have some expiring AWS credits that I want to make use of. It's quite difficult to make large changes while keeping everything backwards compatible, which I'm mostly trying to do. One of the most visible changes at the moment would be how the custom configuration is done. All of the old config options (custom-patches, custom-manifest-remotes, custom-manifest-projects, custom-prebuilts) would be deprecated in favor of a custom configuration repo, which is just a git repo that is formatted in a specific way that defines all the customizations you want in one place. The existing custom configuration options are a pain to deal with in config and not very flexible. The new method requires a bit more technical expertise to setup but has much more flexibility. It also has the added benefit of matching close to how CalyxOS does their vendor repo, so it is easier to borrow things from their project.