[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Files that don't belong in CVS
|
Mostly +1. These are build products, and as such, don't belong in
our repository. (Now, if we had a repository with audited builds,
that would be a different story, but we don't.
The one problem is that I'm trying to move to a build process that
uses the Eclipse build files. If we don't include those, then we make
it impossible for non-Eclipsers to build the system.
Perhaps the appropriate thing is to put minimal hand-written build files
into the project directories that *don't* get changed by Eclipse, and
that don't include the platform specifics? In other words, create a
manual build process that parallels the Eclipse one, but doesn't use
the same build files?
-Mark
On Tue, 2003-02-11 at 14:43, Jim Wright - IBM Research wrote:
> In the course of generating my recent patches, I tripped over a number of
> files that really don't belong in CVS.
> These include:
>
> Eclipse-generated build.xml files
> (because they contain platform- and window-toolkit- specific properties)
> All contents of 'bin' folders
> All contents of 'build' folders
>
> The presence of these files complicate patch generation and increase the time
> it takes to sync with the repository.
>
> I would like to delete them from our CVS repository (and ask committers to
> avoid checking them in in future).
>
> Comments? Votes for/against?
>
> Thanks,
> Jim
> --
> Jim Wright, IBM T.J. Watson Research Center
> *** The Stellation project: Advanced SCM for Collaboration
> *** http://www.eclipse.org/stellation
> *** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
> jim.wright@xxxxxxx
>
> _______________________________________________
> stellation-res mailing list
> stellation-res@xxxxxxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/stellation-res
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxxxxxx
