subversion repository plans libraries grown opposing opposite programs
i'm grateful several (rather small) programs, share lot formula around opposite libraries. i'm wondering best repository plans arise opposite prorgrams (and libraries), keep libraries sync opposing programs.
for effect justification let's contend there twin programs twin libraries:
- program1
- library1
- library2
- program2
- library1
- library2
naturally, bug fixes enhancements libraries should (eventually) combine programs. given libraries being worked while operative opposite programs, controlling seems out question.
so i guess provide libraries during nonetheless place nonetheless i'm certain best plans be.
i pondering something along lines of:
- libraries
- library1 (ancestor)
- library2 (ancestor)
- program1
- program1 code
- library1 (vendor branch)
- library2 (vendor branch)
- ...
then contend building program1 changes finished library2, i combine behind libraries biased repository, combine there programs desired.
merging programs can't always occur immediately, operative program2 tie redeem rather finish first, emanate tag, wholly following transform libraries.
i'm bit concerned outcome merges bit maintain headache after while nonetheless i don't unequivocally many improved solution.
then again, seems rather common box me, i guess i'd only ask community, what's best repository plans grasp this?
Comments
Post a Comment