Both static linking and embedded copies have similar issues.
With static linking you have to track where the static library ended up (recursively) and then issue rebuilds in the correct order for all packages that contain the static library (directly or indirectly).
With embedded copies you have to search the source code archive for the copies and then patch and rebuild each copy.
In some ways static linking is more complicated to deal with, due to the case that the static library ends up in some other static library.
pabs3|5 years ago
With static linking you have to track where the static library ended up (recursively) and then issue rebuilds in the correct order for all packages that contain the static library (directly or indirectly).
With embedded copies you have to search the source code archive for the copies and then patch and rebuild each copy.
In some ways static linking is more complicated to deal with, due to the case that the static library ends up in some other static library.