Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #27152 > unrolled thread
| Started by | andrea crotti <andrea.crotti.0@gmail.com> |
|---|---|
| First post | 2012-08-16 11:57 +0100 |
| Last post | 2012-08-16 11:57 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Sharing code between different projects? andrea crotti <andrea.crotti.0@gmail.com> - 2012-08-16 11:57 +0100
| From | andrea crotti <andrea.crotti.0@gmail.com> |
|---|---|
| Date | 2012-08-16 11:57 +0100 |
| Subject | Re: Sharing code between different projects? |
| Message-ID | <mailman.3353.1345114651.4697.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web