Re: How to organize multiple small reusable components with Git?
Hi Bing, I don't think the approach you're outlining in your most recent e-mail is going to work particularly well for you. See my replies in-line. I have devised a solution that should work much better for you, it's a tiny bash script and a set of naming conventions for repository branches. I've described it in detail and implemented a toy example on github: https://github.com/picrin/git-components/blob/master/README.md FYI, when you click reply button, you have to click reply all or otherwise your e-mail doesn't go to the mailing list but just to me personally. Inline responses follow: > Thanks for your kindly reply, which helps a lot. > I plans a neutral approach for my case now. > (1) create a "Components" git repo to hold all kinds of components, > each component in a directory. > As for each component, use regular git way to manage the version. > Accordingly there's not Version1 (Dir) or Version2(Dir), to follow Git > practice. This way you can't version each component independently -- you have one global history, which means a lot of noise per component. > (2) create another publication (release) server for all versions of > all components. (the server is not managed in git) > The publication server is read only, and every one can get > component(s) they need for further use. It's not clear to me how your publication server would be able to pick up from your messy history the correct versions of multiple components. Also, some of your clients might want to sit on an older (or more stable, or otherwise customised) version of a given component, or want a narrower set of components, so one-history-for-all clearly doesn't work for you. Besides, for publications git has already got something built in, read up about git-archive. Adam > > > > 2015-07-23 20:57 GMT+08:00 Adam Kurkiewicz : >> Hi Bing, >> You seem to be describing a very interesting problem, similar to what I >> often run into in my day job. In my day job I'm composing multiple java >> microservices into a single application. We have about 7 microservices, but >> this number will probably grow to more than 10 before the application is >> feature-complete. Because microservices are mutually independent and unaware >> of each other (however, they _do_ share knowledge of message formats >> exchanged on the message queue), we have a very acute problem of composing >> entire system together. The problem is two-fold: >> >> 1) how do you know which set of the versions of components gives you a >> working system? >> 2) how do you keep track of a record of [the sets of the versions of >> components] which give you a working system? >> >> Part 1) is much more difficult than part 2). Although part 1) lies outside >> of the scope of version control I'd like to pay your attention to it >> nonetheless. In principle with 10 versions of 10 components you have 10 >> billion possibly valid configurations of the system. In such circumstance it >> is very helpful to use such good SE practices like depcrecation warnings, >> semantic versioning and clean distinction between interface and its >> implementation. You can also do it the linux kernel way by simply never >> introducing backwards-incompatible changes. If you want to read up about >> semantic versioning, here's the link to the standard: >> http://semver.org/ >> >> Part 2) is really what git can help you with: >> >> One way to deal with this is to manage each component in a separate git >> repository (thus version each component separately) and have a thin parent >> project, which imports all other projects as submodules. The way submodules >> work is through storing each submodule as a separate directory. You can go >> to each of the submodule directories, checkout a particular commit which you >> want to be marked as a part of your system and mark each component with >> usual command "git add ". That obviously assumes that you've >> already solved Part 1) and you know what versions of components give you a >> working system. You can repeat this process for each submodule and once >> you're happy commit the result in the parent project and push to the remote. >> You can also do usual git things such as tags for example. >> >> I'm not sure how much I like this solution though: having multiple >> repositories seems to be an overkill for most cases. Behaviour of submodules >> has been startling on a few occasions (for example `git submodule update` >> can actually take you to back in time rather than forward). I've also >> experienced several peculiar and difficult to pinpoint issues on windows. >> Although I haven't used it much, git subtrees seems to be much nicer >> alternative. You can read about them here: >> http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ >> >> As to your original idea about having multiple separate directories, I'm not >> sure I like it at all. By splitting the versions of your components into >> separate directories you loose a lot of benefits
Re: How to organize multiple small reusable components with Git?
Hi Bing, You seem to be describing a very interesting problem, similar to what I often run into in my day job. In my day job I'm composing multiple java microservices into a single application. We have about 7 microservices, but this number will probably grow to more than 10 before the application is feature-complete. Because microservices are mutually independent and unaware of each other (however, they _do_ share knowledge of message formats exchanged on the message queue), we have a very acute problem of composing entire system together. The problem is two-fold: 1) how do you know which set of the versions of components gives you a working system? 2) how do you keep track of a record of [the sets of the versions of components] which give you a working system? Part 1) is much more difficult than part 2). Although part 1) lies outside of the scope of version control I'd like to pay your attention to it nonetheless. In principle with 10 versions of 10 components you have 10 billion possibly valid configurations of the system. In such circumstance it is very helpful to use such good SE practices like depcrecation warnings, semantic versioning and clean distinction between interface and its implementation. You can also do it the linux kernel way by simply never introducing backwards-incompatible changes. If you want to read up about semantic versioning, here's the link to the standard: http://semver.org/ Part 2) is really what git can help you with: One way to deal with this is to manage each component in a separate git repository (thus version each component separately) and have a thin parent project, which imports all other projects as submodules. The way submodules work is through storing each submodule as a separate directory. You can go to each of the submodule directories, checkout a particular commit which you want to be marked as a part of your system and mark each component with usual command "git add ". That obviously assumes that you've already solved Part 1) and you know what versions of components give you a working system. You can repeat this process for each submodule and once you're happy commit the result in the parent project and push to the remote. You can also do usual git things such as tags for example. I'm not sure how much I like this solution though: having multiple repositories seems to be an overkill for most cases. Behaviour of submodules has been startling on a few occasions (for example `git submodule update` can actually take you back in time rather than forward). I've also experienced several peculiar and difficult to pinpoint issues on windows. Although I haven't used it much, git subtrees seems to be much nicer alternative. You can read about them here: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ As to your original idea about having multiple separate directories, I'm not sure I like it at all. By splitting the versions of your components into separate directories you loose a lot of benefits of version control. With multiple directories you won't be able to apply hotfixes to multiple versions of the component for example without rewriting the logic of cherry-pick. Cheers, Adam On 23 July 2015 at 12:20, Bing Tian wrote: > I am using git to manage some circuit components. > Each component is small and I plan to create a "component" project in > Git to hold all the small components. > Each component may have several released version, such as > Comonent1_V1, Component1_V2, Comonent2_V1, Component2_V2. > And for future reuse, I may use Component1_V1+Component2_V2, or > Component1_V2+Component2_V1 in my local directory. > So, I plan to create several directories, each for one version of one > component. I looks like followings: > Components > |--Component1 > | |--Version1(Dir) > | |--Version2(Dir) > |---Component2 >|--Version1(Dir) >|--Version2(Dir) > > I want to know, is the above a suitable way in Git? Are there some > risks for my project and Git? > Any suggestions to cover this case in Git? > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
How to organize multiple small reusable components with Git?
I am using git to manage some circuit components. Each component is small and I plan to create a "component" project in Git to hold all the small components. Each component may have several released version, such as Comonent1_V1, Component1_V2, Comonent2_V1, Component2_V2. And for future reuse, I may use Component1_V1+Component2_V2, or Component1_V2+Component2_V1 in my local directory. So, I plan to create several directories, each for one version of one component. I looks like followings: Components |--Component1 | |--Version1(Dir) | |--Version2(Dir) |---Component2 |--Version1(Dir) |--Version2(Dir) I want to know, is the above a suitable way in Git? Are there some risks for my project and Git? Any suggestions to cover this case in Git? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
