On 3/21/07, Karl Fogel <email@example.com> wrote:
> "Mark Phippard" <firstname.lastname@example.org> writes:
> > Today's crowd on IRC seems to prefer this original idea, rather than
> > put files in trunk. So I have attached a patch that is more specific
> > in terms of what I am proposing. Based on IRC discussions, I have
> > altered this a little. Instead of using svn:externals to pull in the
> > Subversion code, I added an empty folder named "src". I would include
> > a README file, that is not in the patch that would instruct the user
> > to use the switch command to switch src to trunk or the branch of
> > their choice.
> Wait, so there's going to be a 'trunk/src/' directory now? And it's
> not going to contain Subversion source code? If I'm misunderstanding,
> please let me know... if not, it sounds like it'll be a bit confusing
> for people trying to figure out what's where in our tree.
This patch was not against trunk. It would put files completely be outside
trunk. The src folder would exist so that the user would have something
that they could use svn switch on to pull in trunk. This was because some
people in IRC expressed a preference to this technique over the use of
svn:externals. It certainly makes it easier to reuse the same project for
trunk and/or any branch in the repository.
Right now there are three proposals:
1) Just stick the needed files in the root of trunk. I sent a separate
patch for that (same name file though sorry).
2) Create project folder outside of trunk. I suggested in the
"developer-resources" folder off the root of the repostiory. This project
would contain the Eclipse files and an empty src folder that the user could
switch to trunk or a branch of choice.
3) Same as #2, except use svn:externals to pull in trunk.
In each case, the Eclipse files needed are essentially the same. Each
approach just varies where they would be put in the repository. I like
option #1 the best, but it does potentially set a bad precedent as people
potentially want to use other IDE's in the future.
Can these files do includes of other files? If so, another solution
> might be to put one file at the top of trunk/, with just an include
> line that pulls in other files at less egregious locations.
I am pretty sure the answer is no.
Received on Thu Mar 22 03:21:19 2007