[Please post inline, it makes it easier to follow...]
> -------- Message original --------
> Sujet: Re: Question about subversion
> De : Cooke, Mark <mark.cooke_at_siemens.com>
> Pour : Marc Davenne <marc.davenne_at_cramif.cnamts.fr>, Andrew Reedick
> <Andrew.Reedick_at_cbeyond.net>
> Copie à : "users_at_subversion.apache.org" <users_at_subversion.apache.org>
> Date : 27/06/2013 11:40
>
> >> -----Original Message-----
> >> From: Marc Davenne [mailto:marc.davenne_at_cramif.cnamts.fr]
> >> Sent: 27 June 2013 10:25
> >> To: Andrew Reedick
> >> Cc: users_at_subversion.apache.org
> >> Subject: Re: Question about subversion
> >>
> >> Thank you for your answers... all of you
> >>
> >> @Andrew
> >> Thank you, the answers you gave were exactly what I thought
> >> about (I was
> >> a little bit too general when I asked the question)
> >>
> >> - concerning answer number 2 (specific files)
> >> Let's say I have a parameter file with paths for my dev
> environement.
> >> Typically I would not put it on svn because everybody has different
> >> ones... but how to I version the param file (without it the
> >> application does not work)
> >
> > I think it was BOb who gave an answer for that one... What
> I do is to svn:ignore the file itself, then check in a
> default version with a different filename (e.g. extra `.tmpl`
> extension) and provide some sort of `initialisation` script
> that can be used on fresh checkout to copy the template
> file(s) to the right name(s) for use.
> >
> > For exmaple, I have several .ini files to target different
> servers (development, test, site1, site2 etc) all checked in
> with the actual .ini file name ignored. I then copy the
> right one for what I want to the right name. The different
> ini fils are then versioned in the repo.
> >
> > ~ mark c
> -----Original Message-----
> From: Marc Davenne [mailto:marc.davenne_at_cramif.cnamts.fr]
> Sent: 27 June 2013 11:15
> To: Cooke, Mark
> Cc: Andrew Reedick; users_at_subversion.apache.org
> Subject: Re: Question about subversion
>
> I am not sure I understand it very well. When you say it is ignored,
> does it mean it is on svn ?
The subversion book explains svn:ignore better than I will:-
http://svnbook.red-bean.com/en/1.7/svn.advanced.props.special.ignore.html
In summary: this is a way to tell svn to ignore a file (or filename pattern) when looking for files to check-in. Hence the file itself is not in the repo, but your template version(s) is (are).
> And what is this script that would trigger on checkout ?
That would be (for me, on windows) a simple batch file (that is also checked in) that the user knows to run.
> Can you explain it again ?
Does that help?
~ mark c
Received on 2013-06-27 12:51:35 CEST