RTEMS | Better seperation of 3rd party code (#5294)

[Christian Mauderer (@c-mauderer)]

Christian Mauderer commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5294#note_126166


I think the suitable method depends a lot on the goals.

>From your issue description, I think some are:
- Easy maintenance (updating to newer versions, maintaining necessary patches)
- Clear separation to make it simpler to ignore third party sources during updates

Additionally, some could be:
- Keeping code with different license (Apache, MIT, ...) clearly separated so we don't have to think about where to put a LICENSE file or how to handle SPDX headers.

Difficulties are:
- How to handle that code during releases?
- How to make sure that the code / library is there during build?

Personally, I would prefer to use submodules. But I know that it's not everyones favorite.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5294#note_126166
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250708/79fb0023/attachment.htm>