From users-return-64-daniel=haxx.se@subversion.apache.org Thu Dec 17 14:39:41 2009 Return-Path: Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by giant.haxx.se (8.14.3/8.14.3/Debian-9) with SMTP id nBHDdeqh002819 for ; Thu, 17 Dec 2009 14:39:40 +0100 Received: (qmail 11518 invoked by uid 500); 17 Dec 2009 13:39:35 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 11510 invoked by uid 99); 17 Dec 2009 13:39:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 13:39:35 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [80.67.18.15] (HELO smtprelay03.ispgateway.de) (80.67.18.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 13:39:26 +0000 Received: from [75.60.181.128] (helo=[192.168.7.75]) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1NLGZN-0008VY-2V; Thu, 17 Dec 2009 14:39:05 +0100 Subject: Re: Ideal Subversion Setup Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Ryan Schmidt In-Reply-To: <4B29FFA9.4070800@ephotozine.com> Date: Thu, 17 Dec 2009 07:39:02 -0600 Cc: users@subversion.apache.org Content-Transfer-Encoding: quoted-printable Message-Id: <3E2AB421-84BB-4ACC-9B89-FD3F0D10146E@ryandesign.com> References: <4B290429.8090706@ephotozine.com> <40AAACFF-BE17-44B7-8513-319B851E53CF@ryandesign.com> <4B29FFA9.4070800@ephotozine.com> To: David Burleson X-Mailer: Apple Mail (2.1077) X-Df-Sender: 368818 X-Virus-Checked: Checked by ClamAV on apache.org On Dec 17, 2009, at 03:53, David Burleson wrote: > Let me elaborate on our setup. I've decided the first thing to do is = to cut out the inbetween step of dragging files over. So I have setup a = folder on our local linux webserver and setup apache web server to use = it as a virtual host (to do testing). This works great. Now I need to = sort out the symlinks for the images directory. We create the symlinks = manually through command line (ssh). We are using TortoiseSVN as a way = to create the checkout to be used on our Windows computers. So.... >=20 > 1. Linux Server: create a directory for development area > 2. Linux Server: setup apache to use the newly created directory as a = virtual host > 3. Windows PC: Browse to the newly created directory via the network > 4. Windows PC: Right click on the directory and select SVNcheckout and = checkout the repository > 5. Linux Server: Create a symlink in the directory to another = directory on the linux server >=20 > So...how do I commit that symlink as a symlink and not commit the = contents within it? Ah, you didn't mention before that there were two computers and two = operating systems involved. You said before: >>> I have been using subversion with TortoiseSVN for a couple of years = now. [...] We currently each have our own development area on a local = web server for each project. I assumed the machine where you are using TortoiseSVN is the same = machine where you have the working copy and the same machine where the = web server is running. To commit the symlink, you will need to run "svn commit" on the Linux = server, not on the Windows machine, since as I mentioned, the Windows = operating system has no concept of symlinks and cannot represent them. What you are doing -- having a working copy on a Linux server and = manipulating it via TortoiseSVN on Windows (presumably via a Samba = share) -- can work. We did this in a web programming shop where I = worked. But you must be careful to avoid the differences that exist = between platforms. That means avoiding symlinks, avoiding svn:eol-style = native, avoiding case-only name collisions, avoiding reserved Windows = filenames and extensions, etc. The official party line is that you = should only work with a working copy on the same OS it was checked out = on. Maybe this explains a bit the reasons for your original process of = manually copying the files. > And, what is the best way to preserve folder/dir permissions using = chmod into a repository? It is not possible to preserve permissions in a Subversion repository, = except for the aforementioned executable bit via the presence or absence = of the svn:executable property.