You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Erich Enke <ep...@ruffdogs.com> on 2004/12/02 15:58:43 UTC
checkout-specific config files: svnadmin readonly??
My problem is this:
We have subversionized our PHP webapp projects, but each installation,
each checkout, requires different config files (to specify your
database, username, password, etc). We would like our project to have
default files with comments, basically vanilla config files. However,
with multiple developers working on a project, each with their own
checkouts and database information, that means that that
version-controlled config file wants to be checked once the checkout is
customized to that user and thereafter.
Is there some way to svn ignore that file, so that, although it is under
version control, it won't be checked in after you tell it to ignore that
file? (I don't want to remove the file from version control because the
vanilla version should be in there)
Is there some way to specify at the repository level, "Hey, this file is
read only!! Only check out versions of this file, don't commit unless
explicitly told to." ?
Is there some nifty trick on how to use subversion or good
packaging/project practice to achieve this desired behavior?
Thanks,
Erich Enke
Ruffdogs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: checkout-specific config files: svnadmin readonly??
Posted by Erich Enke <ep...@ruffdogs.com>.
Erich Enke wrote:
> that means that that version-controlled config file wants to be
> checked once the checkout is customized to that user and thereafter.
>
Should be "that means that that version-controlled config file wants to
be checked *in* once the checkout is customized to that user and thereafter.
Erich Enke
Ruffdogs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: checkout-specific config files: svnadmin readonly??
Posted by Erich Enke <ep...@ruffdogs.com>.
François Beausoleil wrote:
>
>
> Erich Enke wrote:
>
>> Is there some way to svn ignore that file, so that, although it is
>> under version control, it won't be checked in after you tell it to
>> ignore that file? (I don't want to remove the file from version
>> control because the vanilla version should be in there)
>
>
> Quoting http://subversion.tigris.org/project_faq.html#ignore-commit
>
> ----------
> I have a file in my project that every developer must change, but I
> don't want those local mods to ever be committed. How can I make 'svn
> commit' ignore the file?
>
> The answer is: don't put that file under version control. Instead, put
> a template of the file under version control, something like "file.tmpl".
>
> Then, after the initial 'svn checkout', have your users (or your build
> system) do a normal OS copy of the template to the proper filename,
> and have users customize the copy. The file is unversioned, so it will
> never be committed. And if you wish, you can add the file to its
> parent directory's svn:ignore property, so it doesn't show up as '?'
> in the 'svn status' command.
> ----------
I'm pretty sure this is what I'm looking for. Thank you for all the
speedy replies.
Erich
Ruffdogs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: checkout-specific config files: svnadmin readonly??
Posted by François Beausoleil <fb...@ftml.net>.
Erich Enke wrote:
> Is there some way to svn ignore that file, so that, although it is under
> version control, it won't be checked in after you tell it to ignore that
> file? (I don't want to remove the file from version control because the
> vanilla version should be in there)
Quoting http://subversion.tigris.org/project_faq.html#ignore-commit
----------
I have a file in my project that every developer must change, but I
don't want those local mods to ever be committed. How can I make 'svn
commit' ignore the file?
The answer is: don't put that file under version control. Instead, put a
template of the file under version control, something like "file.tmpl".
Then, after the initial 'svn checkout', have your users (or your build
system) do a normal OS copy of the template to the proper filename, and
have users customize the copy. The file is unversioned, so it will never
be committed. And if you wish, you can add the file to its parent
directory's svn:ignore property, so it doesn't show up as '?' in the
'svn status' command.
----------
Hope that helps,
François
Re: checkout-specific config files: svnadmin readonly??
Posted by Ben Collins-Sussman <su...@collab.net>.
On Dec 2, 2004, at 9:58 AM, Erich Enke wrote:
>
> Is there some way to svn ignore that file, so that, although it is
> under version control, it won't be checked in after you tell it to
> ignore that file?
FAQ: http://subversion.tigris.org/project_faq.html#ignore-commit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: checkout-specific config files: svnadmin readonly??
Posted by Johan Appelgren <jo...@appelgren.org>.
> Is there some nifty trick on how to use subversion or good
> packaging/project practice to achieve this desired behavior?
>
http://subversion.tigris.org/project_faq.html#ignore-commit
Is that what you're looking for?
/Johan Appelgren
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org