> > I have one big project, in which under it has many
> > modules to be created by many different
> Ok, makes sense.
> > Maybe I said it wrongly. The directory layout in
> > apache's doc root is:
> > /Project/common/module1
> > /Project/common/module2
> > /Project/html/module1
> > /Project/html/module2
> > The above layout is not the repository layout. I
> > don't know how to layout the repository.
> Alright, so let me see if I understand this
> correctly. The layout
> above is the layout of the project as it will be
> accessed from a web
> browser, though Apache, correct?
Yes. That's how it looks like in the Apache docroot.
> What you want to know is how to layout a repository
> to have developers
> work on the individual modules, right?
Exactly. And also how they check out later, because
of the problem I elaborate below
> > One problem that I've thought of is, how do each
> > developers checkout their modules so that it falls
> > into place following the above directory
> > They would have to do a checkout of
> > /Project/common/module1 and /Project/html/module1.
> > But wouldn't the other developer overwrite the
> > directory when he check out
> > and /Project/html/module2?
> I'm not sure I understand the problem here
> completely. Are all of the
> developers going to be checking out their files in
> the same place? If
> they're going to be checking out to their local
> development machines,
> then the .svn directories won't be an issue, since
> those are only
> created in local working copies.
Ah, yes. I have not stated that they are going to
checkout their files in the same place. They will not
checkout to their local machine. They will check it
out to a common development server with only one
> I think I have a few ideas for what would be the
> best way for you to
> go, but before I take the time to write down my
> suggestions, I want to
> make sure I'm answering the right question. If you
> could elaborate a
> little more on the questions I had above, I'll see
> what I can do to
> help you figure out the best way to proceed.
Thanks! Hope that what I described above gives you
some idea on my situation...
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Aug 4 09:49:35 2004