svn
directories are necessary while keeping content under version control but you may not want them in the final
release, such as, for example if you are going to ftp the contents to a server. Listing 10.8 shows the use of the
export command to get a copy cleaned of all those hidden directories from the repository.
Listing 10.8 Using the export command to get a clean working copy
$ svn export http://www.example.com/svn/places/trunk/ places_export/ A
A places_export
A places_export/web_root
... B
A places_export/db
A places_export/db/test_data.sql
Exported revision 7.
A Note the second path indicating a location for the cleaned working copy
B Output condensed for brevity
Note that having performed the export in listing 10.8, we are left with the same files as we would have had
if we had done a checkout, but since they do not contain the .svn directories they are not under version control.
10.2.2 Externals
While we are moving files between working copies and the repository there is one element that has not been
accounted for; what about the Zend Framework code? We can avoid having to deal with that by mapping one
of our local directories to the external URL of the Zend Framework repository:
svn propedit svn:externals .
application/library/Zend \
http://framework.
Pages:
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293