On making text-base optional

[Ian Anthony <is...@gmail.com>]

I have been using SVN personally since late 2004 and have grown quite fond
of it.  My day job is finally on the brink of transitioning a large code
repos from CVS to subversion, but there is just one issue slowing us down.

Our development model is one where several developers work on multiple
projects at once (4-8 on average).  In our system, each scheduled release
within a project gets its own branch.  This approach puts us right at home
with SVN and its cheap copies considering we might make hundreds of branches
in a year.

The problem for us lies in the fact that most developers check out their
code to the same server the repository is stored on.  Even in a world where
storage is so inexpensive that it should be unending, sometimes it just
doesn't work out that way.  Especially when the coders harddrive fills up
twice as fast as one might expect thanks to text-base.

Twelve developers each working on six copies of one repository on the same
server means a lot of harddrive space is gobbled up in the name of pristine
copies.  I would love to see text-base as an option, especially for
circumstances where network communications aren't the limiting factor.

Thank you and keep up the great work.

--Ian

Re: On making text-base optional

[Duncan Murdoch <mu...@stats.uwo.ca>]

On 9/21/2006 2:13 PM, Ian Anthony wrote:
> It is certainly an option for developers to maintain local copies of the
> repository, but they run into the same issue of gobbling up the storage
> space on their laptop hard drives.

Maintaining a local copy of the repos wouldn't currently help at all 
with the problem you've got:  you'll then have 3 copies of each file on 
each developer's machine:  the working copy, text-base, and the repos 
backup.

As Garrett said, everyone agrees it would be nice if someone else did 
this, but until someone wants it enough to do it, it won't get done.

Duncan Murdoch

> 
> I'll have to make a quick test setup, but I'll bet it would be possible to
> make a script that maintains a cheap checkout library (a library of all
> revisions with cheap copies between each) and then simlink text-base in each
> directory to the library copy for that revision.
> 
> Hmm....
> 
> On 9/21/06, Mark <ma...@mitsein.net> wrote:
>>
>> In the meantime, it would be a good idea to get your developers to use
>> their own machines.  That's where that text-base comes in handy.
>> Since I have my working copy on my own laptop, I can bring it home and
>> keep working without having to log into work if need be.
>>
>> On 9/21/06, Ian Anthony <is...@gmail.com> wrote:
>> > I have been using SVN personally since late 2004 and have grown quite
>> fond
>> > of it.  My day job is finally on the brink of transitioning a large code
>> > repos from CVS to subversion, but there is just one issue slowing us
>> down.
>> >
>> > Our development model is one where several developers work on multiple
>> > projects at once (4-8 on average).  In our system, each scheduled
>> release
>> > within a project gets its own branch.  This approach puts us right at
>> home
>> > with SVN and its cheap copies considering we might make hundreds of
>> branches
>> > in a year.
>> >
>> > The problem for us lies in the fact that most developers check out their
>> > code to the same server the repository is stored on.  Even in a world
>> where
>> > storage is so inexpensive that it should be unending, sometimes it just
>> > doesn't work out that way.  Especially when the coders harddrive fills
>> up
>> > twice as fast as one might expect thanks to text-base.
>> >
>> > Twelve developers each working on six copies of one repository on the
>> same
>> > server means a lot of harddrive space is gobbled up in the name of
>> pristine
>> > copies.  I would love to see text-base as an option, especially for
>> > circumstances where network communications aren't the limiting factor.
>> >
>> > Thank you and keep up the great work.
>> >
>> > --Ian
>> >
>>
>>
>> --
>> Mark
>> "Blessed is he who finds happiness in his own foolishness, for he will
>> always be happy."
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: On making text-base optional

[Ian Anthony <is...@gmail.com>]

It is certainly an option for developers to maintain local copies of the
repository, but they run into the same issue of gobbling up the storage
space on their laptop hard drives.

I'll have to make a quick test setup, but I'll bet it would be possible to
make a script that maintains a cheap checkout library (a library of all
revisions with cheap copies between each) and then simlink text-base in each
directory to the library copy for that revision.

Hmm....

On 9/21/06, Mark <ma...@mitsein.net> wrote:
>
> In the meantime, it would be a good idea to get your developers to use
> their own machines.  That's where that text-base comes in handy.
> Since I have my working copy on my own laptop, I can bring it home and
> keep working without having to log into work if need be.
>
> On 9/21/06, Ian Anthony <is...@gmail.com> wrote:
> > I have been using SVN personally since late 2004 and have grown quite
> fond
> > of it.  My day job is finally on the brink of transitioning a large code
> > repos from CVS to subversion, but there is just one issue slowing us
> down.
> >
> > Our development model is one where several developers work on multiple
> > projects at once (4-8 on average).  In our system, each scheduled
> release
> > within a project gets its own branch.  This approach puts us right at
> home
> > with SVN and its cheap copies considering we might make hundreds of
> branches
> > in a year.
> >
> > The problem for us lies in the fact that most developers check out their
> > code to the same server the repository is stored on.  Even in a world
> where
> > storage is so inexpensive that it should be unending, sometimes it just
> > doesn't work out that way.  Especially when the coders harddrive fills
> up
> > twice as fast as one might expect thanks to text-base.
> >
> > Twelve developers each working on six copies of one repository on the
> same
> > server means a lot of harddrive space is gobbled up in the name of
> pristine
> > copies.  I would love to see text-base as an option, especially for
> > circumstances where network communications aren't the limiting factor.
> >
> > Thank you and keep up the great work.
> >
> > --Ian
> >
>
>
> --
> Mark
> "Blessed is he who finds happiness in his own foolishness, for he will
> always be happy."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

Re: On making text-base optional

[Mark <ma...@mitsein.net>]

In the meantime, it would be a good idea to get your developers to use
their own machines.  That's where that text-base comes in handy.
Since I have my working copy on my own laptop, I can bring it home and
keep working without having to log into work if need be.

On 9/21/06, Ian Anthony <is...@gmail.com> wrote:
> I have been using SVN personally since late 2004 and have grown quite fond
> of it.  My day job is finally on the brink of transitioning a large code
> repos from CVS to subversion, but there is just one issue slowing us down.
>
> Our development model is one where several developers work on multiple
> projects at once (4-8 on average).  In our system, each scheduled release
> within a project gets its own branch.  This approach puts us right at home
> with SVN and its cheap copies considering we might make hundreds of branches
> in a year.
>
> The problem for us lies in the fact that most developers check out their
> code to the same server the repository is stored on.  Even in a world where
> storage is so inexpensive that it should be unending, sometimes it just
> doesn't work out that way.  Especially when the coders harddrive fills up
> twice as fast as one might expect thanks to text-base.
>
> Twelve developers each working on six copies of one repository on the same
> server means a lot of harddrive space is gobbled up in the name of pristine
> copies.  I would love to see text-base as an option, especially for
> circumstances where network communications aren't the limiting factor.
>
> Thank you and keep up the great work.
>
> --Ian
>


-- 
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: On making text-base optional

[Garrett Rooney <ro...@electricjellyfish.net>]

On 9/21/06, Ian Anthony <is...@gmail.com> wrote:
> I would love to see text-base as an option, especially for
> circumstances where network communications aren't the limiting factor.

Nobody disagrees with you.  It would be very nice for the text-base to
be optional, or to be compressed, or to be able to be moved somewhere
outside the working copy for people who have trouble keeping their
tools from messing with it during recursive find/replace operations.
There are a lot of potential features related to the text base, and it
would be great if libsvn_wc could do all of them, but honestly, it's a
complicated bit of code, and this sort of change touches lots of
places in it, so until someone actually steps up to implement the
feature it's not likely to happen.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org