@Ryan Schmidt @Stefan Sperling. I guess that the difficulty of
implementing this depends on how much of the client code depends on
the existence of those files. From the linked bug tracker item, the
answer appears to be 'quite a lot', though I don't know anything about
@Paul Hammant This is used by myself only and I am familiar with
working with SVN and GIT on the command line, but in no way an
'expert'. I prefer tools which are simple and developer focused and
use Linux exclusively, prefer text file configuration.
I mainly work on a desktop but sometimes need to move part of the
file-system onto a laptop and then merge it back again. By file size
most of this data is DSLR raw files and source video, most of which is
related to a website with associated source code. Additionally I have
multiple unrelated personal projects from the past 7 years which need
to be in there own repositories. And miscellaneous 'stuff' which also
needs to stay separate. Some files are interdependent, some are not.
I too have developed a tool to fit my needs, having become
sufficiently frustrated with other tools. However I feel that I'm just
reimplementing part of Subversion, hence the question.
The implementation of this system is very naive, for example storing
it's file manifest as JSON. It also has a number of problems that I
haven't fixed yet. However I've been quite surprised at how well it
works. It handles 16,000 individual files in one of my projects
without difficulty, the biggest bottleneck being the network.
Currently I'm using this to manage the binary stuff and git for code.
I was surprised how easy it was to implement this. The above system is
just over 1000 lines of python and a good chunk of that is a
journaling file-system interface.
On 27 September 2017 at 12:16, Stefan Sperling <stsp_at_apache.org> wrote:
> On Wed, Sep 27, 2017 at 06:01:33AM -0500, Ryan Schmidt wrote:
>> On Sep 26, 2017, at 13:13, Robert Hickman wrote:
>> > I tend to work on projects with a large amount of binary data along
>> > with source code and need to track them together. To this date
>> > Subversion is the only tool that I've used which handles this
>> > dependably. That being said I have one major issue with it - the last
>> > time I used SVN it stored two copies of every file in a checkout. For
>> > what I am doing this additional data is useless. I frequently add new
>> > binary files but rarely modify them in place. It would be extremely
>> > useful for me if there was an option to store only one copy and loose
>> > delta uploads. It's all new data so there is nothing to delta anyway.
>> > As I have not used SVN for several years I realize that this feature
>> > may have been added. If not has it been considered?
>> The feature hasn't been added yet.
> I suspect the only problem with this feature request is that nobody
> has time to work on it :-/
Received on 2017-09-27 18:22:07 CEST