On 12/4/06, Linus Torvalds <torvalds@xxxxxxxx> wrote:
So yeah, it's a bit hacky, but for the reasons I've tried to outline, I
actually think that users _want_ hacky. Exactly because "deep integration"
ends up having so many _bad_ features, so it's better to have a thin and
simple layer that you can actually see past if you want to.
Thin and simple sounds very good. Let's try it with an example. Lets
say we have one apllication App1 and three librarys (Lib1, Lib2, Lib3)
with the following dependency-graph:
App1
/\
/ \
Lib1 Lib2
\ /
\ /
Lib3 (don't really needed for this example but looks nice)
All components can be used individually and have their own upstream,
maintainer etc.
To compile App1 however, I need some files from both Lib1 and Lib2
specifying it's API. To satisfy these dependencies, It sounds
reasonable to link Lib2 and Lib3 submodules from App1. In your
concept, can I construct a modules file to fetch the API files and
their history without checking out the whole Lib1 and Lib2 source?
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html