RE: Update-Only Checkout Enhancement

2013-12-11 Thread Mark Kneisler 
Yes, I understand the export function.  I want functionality for release 
management into test and production environments.  

For these environments I have a few requirements:
Files in these environments will NEVER be edited
For new releases I will need to perform an update to revision, which 
will add, update and delete needed files
I want as small of a .svn directory as possible

I'm fairly certain that this functionality is currently not present, but I 
think there are many installations where this would be valuable.

I'd like to create an enhancement request, but according to the website it was 
recommended that I post to this mailing list first.

-Original Message-
From: Cooke, Mark [mailto:mark.co...@siemens.com] 
Sent: Wednesday, December 11, 2013 1:44 AM
To: Mark Kneisler; users@subversion.apache.org
Subject: RE: Update-Only Checkout Enhancement

 -Original Message-
 From: Mark Kneisler [mailto:mark.kneis...@tceq.texas.gov]
 Sent: 11 December 2013 01:45
 
 I have several environments where I'd like to use a SVN checkout, but 
 where I'd never ever want to make changes to the files or perform a 
 commit.  For these environments, I'd only want to perform an update or 
 an update to revision.
 
 I'm hoping that this type of checkout would require far less space for 
 the .svn directory.
 
AFAIK there is no such option for a checkout, however, you can get the source 
without the .svn folder using the export command:-

http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.export.html

...you can specify the revision etc.  Note, however, that it will not remove 
unwanted files like an update can.

~ mark c

P.s. I think Thorsten just beat me to it...

RE: Update-Only Checkout Enhancement

2013-12-11 Thread Mark Kneisler 
I think making the pristine files optional would work for me.

Here's an idea.

Instead of having pristine copies of all files, how about adding to the 
pristine directory only when a file is changed?

From: Mark Phippard [mailto:markp...@gmail.com]
Sent: Wednesday, December 11, 2013 9:58 AM
To: Mark Kneisler
Cc: Cooke, Mark; users@subversion.apache.org
Subject: Re: Update-Only Checkout Enhancement

On Wed, Dec 11, 2013 at 10:46 AM, Mark Kneisler 
mark.kneis...@tceq.texas.govmailto:mark.kneis...@tceq.texas.gov wrote:
Yes, I understand the export function.  I want functionality for release 
management into test and production environments.

For these environments I have a few requirements:
Files in these environments will NEVER be edited
For new releases I will need to perform an update to revision, which 
will add, update and delete needed files
I want as small of a .svn directory as possible

I'm fairly certain that this functionality is currently not present, but I 
think there are many installations where this would be valuable.

I'd like to create an enhancement request, but according to the website it was 
recommended that I post to this mailing list first.


Pristine files do not exist solely so you can edit files.  It is convenient 
they exist so that you can diff your changes or revert your changes without 
needing to contact the server, or even be online, but obviously those commands 
could be made to use the server for that and simply require a connection when 
no pristine is available.

The main reason the pristine files exist is so that the client and server can 
exchange deltas with each other and minimize network traffic.  This is just as 
true for update as it is for commit.  One of the original mantra's for the 1.0 
release was disk is cheap, network is expensive.

There is an existing request in the system for making these files optional:

http://subversion.tigris.org/issues/show_bug.cgi?id=525

There is also an existing request for storing the pristine files in compressed 
format:

http://subversion.tigris.org/issues/show_bug.cgi?id=908

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

Update-Only Checkout Enhancement

2013-12-10 Thread Mark Kneisler 
I have several environments where I'd like to use a SVN checkout, but where I'd 
never ever want to make changes to the files or perform a commit.  For these 
environments, I'd only want to perform an update or an update to revision.

I'm hoping that this type of checkout would require far less space for the .svn 
directory.