Re: Nested Subversion Checkout
I can see now that my problem is more complex then I thought, not so much in
terms of the implementation, but in terms of deciding how I will accomplish
my goal. I think in the end I will have to go with somehow exporting the
other project into the sites working copy. The whole reason that my boss
here wants us to use subversion and have some sort of automated deployment
at a later date is because now whenever a developer changes something in the
members area code, they must uploaded it to all 15 sites manually using ftp
after testing it. If I tell them that they will have to somehow place the
members area into the other repositories every time they change it (such as
with Vendor branches) then they will say it is just the same as it was
before. I can understand both points though.
I am not sure if I am less confused or more confused now, but as Olivier
said, at least now I have more information to make my decision.
Received on Tue May 15 16:03:31 2007
This is an archived mail posted to the Subversion Users