Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #27152
| References | <CAF_E5JZ82ar7sWi5eOWe46N2wXVAX2QYUb5F9==0dxRbYMsEhg@mail.gmail.com> <20120814215118.GA19167@cskk.homeip.net> <CAF_E5JarppDRD-yuutc1XzFLumWuRvQuf8uZaeQhSw3o7whFFQ@mail.gmail.com> <502CB426.9040302@sequans.com> |
|---|---|
| Date | 2012-08-16 11:57 +0100 |
| Subject | Re: Sharing code between different projects? |
| From | andrea crotti <andrea.crotti.0@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.3353.1345114651.4697.python-list@python.org> (permalink) |
2012/8/16 Jean-Michel Pichavant <jeanmichel@sequans.com>: > > SVN allows to define external dependencies, where one repository will > actually checkout another one at a specific version. If SVN does it, I guess > any decent SCM also provide such feature. > > Assuming our project is named 'common', and you have 2 projects A and B : > > A > - common@rev1 > > B > - common@rev2 > > Project A references the lib as "A.common", B as "B.common". You need to be > extra carefull to never reference common as 'common' in any place. > > JM > Unfortunately I think you guess wrong http://forums.perforce.com/index.php?/topic/553-perforce-svnexternals-equivalent/ Anyway with views and similar things is not that hard to implement the same thing..
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Sharing code between different projects? andrea crotti <andrea.crotti.0@gmail.com> - 2012-08-16 11:57 +0100
csiph-web