Re: Tracking and committing back to Subversion?

From: Sam Vilain <sam@vilain.net>
Date: Feb 10, 2006, 11:16 UTC
Message-ID: <1139570171.12123.29.camel@localhost.localdomain>
In-Reply-To: <200602092301.21098.linuxfood@linuxfood.net>

On Thu, 2006-02-09 at 23:01 -0800, Brian Smith wrote:

Show 11 quoted lines

> > > While that is an admirable goal, unless you can point me to something
> > > that will allow you to actually commit back to SVN without a working
> > > copy,
> > Such as SVK
> >    http://svk.elixus.org/
> >    (svn url: http://svn.openfoundry.org/svk/)
> Well, after reading through a number of pages I discovered something:
> "The repository created is actually a Subversion repository. In other words, 
> you could use any subversion commands with that repository." [*1*]
> So, while it is a technicality, there is an SVN Repo, which is what
> I'm trying to avoid[...

Yes, currently there is - but let me show you what's under the hood briefly... as you notice later;

> (Incidentally, the allure of the SVN perl bindings had me for awhile, but 
> after trying to decipher the horrid PODs for it decided that Bash was just 
> easier. )

Yes, there are SWIG bindings for various languages. In debian/ubuntu the Perl bindings will be built to the package libsvn-core-perl.

Take a look at this module:

  http://search.cpan.org/dist/SVN-Simple/lib/SVN/Simple/Edit.pm

That uses the above module and allows you to construct a Subversion commit and try to apply it.

The documentation's a bit weak, but AFAIK the basic functionality is there and a lot better an abstraction than the raw bindings themselves.

SVN::Mirror:

  http://search.cpan.org/dist/SVN-Mirror/lib/SVN/Mirror.pm

can go the other way.

> (the point being to have a git repo after all, for
> the purpose of using git commands), perhaps it would be worth looking
> into to see if I could somehow utilize the svk svn repo (since there
> are space savings) for the SVN working copy. [*2*]

That's right - in principle, SVK could be plumbed to have a git repository in its ~/.svk/local - then you could have one git repo, and a head for each mirrored project.

But don't concern yourself with my plans - it seems our tastes in porcelain differ ;)

Sam.