You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by mq...@nlxcorp.com on 2003/10/23 22:07:55 UTC
Files that should not be updated
Hello,
I'm currently porting our razor source format to a subversion repository
and have the following issue:
The repository includes everything that a developer needs to begin work on
the code so that when the developer executes
the checkout command all files are there. This includes Makefiles and DEP
files used to build the code. This files must be
tailored by each developer depending on their working circumstance so after
checking out a load they'll edit them to include their
configurations. This then causes problems with the repository because when
a developer runs the "svn update" command s/he's
told that the files are in conflict, etc. Is there a way to have subversion
NOT keep track of file versions on specified files in the
repository?
Thanks.
Marco Quezada
Aerospaceo Engineero
NLX Corporation
22626 Sally Ride Dr.
Sterling, VA, 20164
703-234-2100 ext. 1028
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Files that should not be updated
Posted by Ben Collins-Sussman <su...@collab.net>.
mquezada@nlxcorp.com writes:
> Is there a way to have subversion NOT keep track of file versions on
> specified files in the repository?
Yes -- just don't put the files in the repository.
Honestly, either files are under version control, or they're not.
Subversion has no problem if your working copy contains unversioned
files. You can even describe the files in the svn:ignore property, so
that 'svn status' won't notice them at all.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Files that should not be updated
Posted by Paul Gross <pa...@grosss.net>.
What if you just check in a file which generates the initial file(s) you
want. For example, check in "generate-settings.py" When this program is
run, it creates a file called "my_settings.txt," which is ignored by
svn. Then, make your build process check for the existence of
"my_settings.txt" and if it doesn't find it, runs "generate-settings.py"
I think this solves all of your problems. The developers don't have to do
anything initially, and subversion ignores the settings file like you want.
Paul Gross
paul@grosss.net
At 06:11 PM 10/23/2003, Jack Repenning wrote:
>At 6:07 PM -0400 10/23/03, mquezada@nlxcorp.com wrote:
>>Hello,
>>
>>I'm currently porting our razor source format to a subversion repository
>>and have the following issue:
>>
>>The repository includes everything that a developer needs to begin work on
>>the code so that when the developer executes
>>the checkout command all files are there.
>>...
>>This then causes problems with the repository because when
>>a developer runs the "svn update" command s/he's
>>told that the files are in conflict, etc. Is there a way to have subversion
>>NOT keep track of file versions on specified files in the
>>repository?
>
>You want the files to be managed by SVN initially, "so that when the
>developer executes the checkout command all files are there," but then
>later, at update, you want them *not* there?
>--
>-==-
>Jack Repenning
>CollabNet, Inc.
>8000 Marina Boulevard, Suite 600
>Brisbane, California 94005
>o: 650.228.2562
>c: 408.835.8090
>f: 650.228.2501
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Files that should not be updated
Posted by Jack Repenning <jr...@collab.net>.
At 6:07 PM -0400 10/23/03, mquezada@nlxcorp.com wrote:
>Hello,
>
>I'm currently porting our razor source format to a subversion repository
>and have the following issue:
>
>The repository includes everything that a developer needs to begin work on
>the code so that when the developer executes
>the checkout command all files are there.
>...
>This then causes problems with the repository because when
>a developer runs the "svn update" command s/he's
>told that the files are in conflict, etc. Is there a way to have subversion
>NOT keep track of file versions on specified files in the
>repository?
You want the files to be managed by SVN initially, "so that when the
developer executes the checkout command all files are there," but
then later, at update, you want them *not* there?
--
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835.8090
f: 650.228.2501
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org