On 5/28/07, Holger Schulz <qdl@gmx.net> wrote:
> > With text files, you would get a line-by-line diff, but it can't
> > show you that with binary files since it doesn't know how to
> > interpret binary formats.
>
> Does that mean, that subversion does recognize which data is binary
> and which can be understood as text? Or do have to tell subversion
> what is what?
Subversion does internal diffs identically, whether it's a binary or
text file. The difference comes in when you want to *review* the diffs
- you can't do it without extra tools that are specific to that
filetype.
It is a good idea to give Subversion, other software, and other
people, an indication of what the filetype is via the svn:mime-type
property.
> > Note that many will recommend not storing generated files in the
> > repo. In your case, if the PDFs are generated from the LaTeX files,
> > then store the LaTeX files in the repo along with a script that
> > generates the PDFs, but not the PDFs themselves.
>
> And that script would generate the PDF file on checkout? I'm not sure
> if I understood this point.
The current release of Subversion has no built-in ability to run
scripts upon checkout. What Ryan was getting at is that rather than
keep binaries (which tend to be larger than their sources, and can't
be visually diffed easily) in the repository, one usually only keeps
the means by which to produce those files in the repository (the
source and the build script). So your workflow would be:
1) Checkout/update
2) Run LaTeX to PDF script
3) Do whatever with the PDFs.
You could also write your own wrapper to do the checkout or update,
then run the script automatically.
>
> >> 2. Currently I have a G4 desktop which holds the repositories. I also
> >> have a PowerBook which I you for work at home and from outside. At
> >> home I connect the desktop from the book via its Bonjour name
> >> <something>.local, to connect it within my local net. From outside I
> >> have to use a global name (in this case via dyndns). So the problem
> >> appears that the same repository might apear under two different
> >> names. How can I tell the working copy that its repository has
> >> "moved"?
> >
> > In the working copy:
> >
> > svn switch --relocate $OLDPREFIX $NEWPREFIX
> >
> > where $OLDPREFIX and $NEWPREFIX are the parts of the URL that
> > changes. For example, if you're relocating from svn://foo.local/
> > repo to http://foo.dyndns.org/repo then you could issue
> >
> > svn switch --relocate svn://foo.local http://foo.dyndns.org
>
> I'll try that.
To answer your later question, yes you can change protocol as well as the URL.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 28 14:42:39 2007