Cleaning up proprietary-files.txt

[dk1978]

I would suggest we move all .conf, .xml and any other text files out of proprietary-files.txt and use our own copy in the device tree plus the mechanisms in device.mk to copy files into place. Are you willing to go ahead with this, since you have already worked in this direction?

Second, do you know of a way to check if we are copying AOSP artifacts from the vendor image that we could be building from source ourselves?

[mstaz]

I would suggest we move all .conf, .xml and any other text files out of proprietary-files.txt and use our own copy in the device tree plus the mechanisms in device.mk to copy files into place. Are you willing to go ahead with this, since you have already worked in this direction?

Yes, totally agree on that.

Second, do you know of a way to check if we are copying AOSP artifacts from the vendor image that we could be building from source ourselves?

No, unfortunately not. I guess we'd manually walk through all of them and check for the sources and how to build it accordingly. Furthermore I fear that some stuff is really qcom proprietary where no sources are available.
However sooorajjj from the /e/ development team told me that they are using this manifest as base. I checked for sources here sometimes, but so far I couldn't find anything here that is missing in the LOS repos.