WC-NG - on detachable WCs and pristine store options [was: Changing the "native" newline mode]

[Julian Foad <ju...@wandisco.com>]

Just changing the Subject line to match the topic of conversation.

- Julian


On Mon, 2010-02-15 at 01:43 +0100, Stefan Sperling wrote:
> On Sun, Feb 14, 2010 at 07:31:07PM -0500, Glenn Maynard wrote:
> > On Sun, Feb 14, 2010 at 6:47 PM, Mark Mielke <ma...@mark.mielke.cc> wrote:
> > > Heck, if one can ask the server for missing pristine copies - why not treat
> > > it like a "least recently used" cache, where users can cap the shared
> > > pristine copy to a certain size, and it will download the missing pristine
> > > copies as required when it needs them, rather than always keeping everything
> > > local?
> > 
> > Putting aside shared data, being able to tell Subversion to go back to
> > CVS's "download the prestine copy as needed" behavior (eg. a
> > "svn:no-cache" property) would be extremely useful.  For large
> > compressed binaries (eg. .ogg files, the bulk of my large data),
> > binary diffs are utterly useless, so the benefits of the prestine
> > files around are mostly lost (except for, off-hand, svn revert).  For
> > me, this would solve the prestine-overhead problem completely.  If you
> > have many gigs of data that *can* be diffed, however, it obviously
> > wouldn't be as effective for you as shared prestine data would be.
> 
> Making the pristine store optional should be easy and I've seen
> this mentioned before:
> http://subversion.tigris.org/issues/show_bug.cgi?id=525#desc19
> 
> > On Sun, Feb 14, 2010 at 7:14 PM, Stefan Sperling <st...@elego.de> wrote:
> > > As I said, I don't expect pristines to clean up themselves.
> > 
> > Sorry; if you said that, I missed it and can't find it.
> 
> I was not explicit about it in my first reply. It was between the lines,
> and in my head :)
> 
> > > But if it's not a design goal, then there's no point in complaining
> > > when the feature goes away. Either the feature is part of the design
> > > or it isn't.
> > 
> > It's a use case that's always been handled by SVN and CVS.  When you
> > have a feature that's been supported for that long, which real users
> > expect to be able to do, then it's an oversight in the design if it
> > doesn't mention it.  That doesn't make it any less of a real use case
> > whose support is disappearing.  (Fortunately, it's a relatively minor
> > use case; I'll survive.)
> 
> I agree that, in general, it sucks if something suddenly stops working.
> And I also think people missing this feature will survive.
> 
> Stefan

Re: WC-NG - on detachable WCs and pristine store options

[Stefan Sperling <st...@elego.de>]

On Sun, Feb 21, 2010 at 09:24:20PM +0100, Steinar Bang wrote:
> > On Mon, 2010-02-15 at 01:43 +0100, Stefan Sperling wrote:
> 
> >> Making the pristine store optional should be easy and I've seen
> >> this mentioned before:
> >> http://subversion.tigris.org/issues/show_bug.cgi?id=525#desc19
> 
> I think optional pristine store needs to be possible to control on the
> file level.  Not just on or off.

This would be like telling svn to not ever cache the pristine
text for some particular file. Fine, I can see use cases for this.
But what kind of interface would you like to control this?

"Don't ever cache foo.c"!
What if another WC uses foo.c as well?

"Don't ever cache the file with the checksum 49f910..." ?
Bit inconvenient... ?

> On a different note, the bug comment, the above URL is a response to
> mentions: "open subversion up to new markets: home backup and
> multiple-computer synchronization"
> 
> I use svn for some of that: I version parts of my home directory, mostly
> config files, but also some replicated ordinary files.

Using svn for this does not make it a first class use case :)
If people use svn for this, fine. But svn isn't rsync, so if rsync does
this better, use rsync.

> One thing I'm missing for my use case is the possibility to persist
> write privileges (I have some files with login secrets that I would like
> to be set to go-rwx, or the equivalent).

You can't possibly be the first person to bring this up during the last
10 years. I'm not sure what prior discussions about this topic ended up
with, but maybe searching the archives would give some answers.

Stefan

Re: WC-NG - on detachable WCs and pristine store options

[Steinar Bang <sb...@dod.no>]

> On Mon, 2010-02-15 at 01:43 +0100, Stefan Sperling wrote:

>> Making the pristine store optional should be easy and I've seen
>> this mentioned before:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=525#desc19

I think optional pristine store needs to be possible to control on the
file level.  Not just on or off.

On a different note, the bug comment, the above URL is a response to
mentions: "open subversion up to new markets: home backup and
multiple-computer synchronization"

I use svn for some of that: I version parts of my home directory, mostly
config files, but also some replicated ordinary files.

One thing I'm missing for my use case is the possibility to persist
write privileges (I have some files with login secrets that I would like
to be set to go-rwx, or the equivalent).

(I'm aware of fsvs but it's not really appropriate to my use case)