"Mark Phippard" <markphip@gmail.com> 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.
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.
> The patch is adding a new folder named eclipse-project to the
> developer-resources folder off the root of the repository. This
> folder contains the Eclipse project files. A user could checkout this
> folder in Eclipse, then use the switch option inside Eclipse to pull
> in the source code. I cannot test this until the files are in the
> repository, so I may have to tweak a few things after the initial
> commit. Conceptually it should work though and using switch has
> benefits over externals, not the least of which is making it easy to
> change between trunk and a branch.
I like the general plan, it's just that directory name "src" that's
gnawing at me... :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 22 03:13:54 2007