FW: Summary of a IRC conversation in #zynot-infra

> From: Amir Guindehi [mailto:[email protected]]
> Sent: Monday, August 11, 2003 10:54 AM

> Sander Striker wrote:

[...]
>> So either the correct ebuilds with their dependencies should be published
>> somewhere on the zynot.org domain with instructions, or, we should give
>> instructions how to build from source...
> 
> Those Ebuilds are published on the following website:
> 
> https://gentoo.datacore.ch/DCwiki.gentoo/Ebuild.jsp?page=DataCore.EBuilds&portage=dc.gentoo

Right.  Like I said, we need to publish them on the zynot.org domain.

>>> At this point the only way to get a working SVN is to pull and entire
>>> overlayed tree with Amir's gentoo based tree.
>>
>> Come on.  That's certainly not the only way.  If you download a
>> Subversion release tarball and read INSTALL you come a very long way.
>> Especially if you don't need to build a server.
> 
> *rol*
> 
> I, personally, would advice to download the needed Ebuilds!
> 
> There are not _that much_ dependencies (neon,

> db-4.0.14,

For a client not a required dependency.

> autoconf, libtool, bison, python,

> diffutils,

Not a required dependency.

> openssl,

If you wish to use the https:// schema (which you do for zynot).

> texinfo, texi2html),

Not a required dependency.

> Sander, building sources by hand is bad! ;-))

Bad, Good, Ugly, whatever.  I'm just saying that you are not unable
to get Subversion to install without an ebuild.

> I, personally, even write XXX-svn.ebuilds first, so that compiling my 
> own sources while developing becomes a simple 'emerge XXX-svn.ebuild.
>
> BTW:  The Eclass for Subversion with the name svn.eclass is available 
> only by pulling the whole tree.
> 
>> If you do a regular svnadmin dump $REPOS > dumpfile, you are always
>> able to recover your data.  People who are less paranoid can backup
>> their svn repository using the hot-backup script included with
>> Subversion.
> 
> I wrote a SVN backup script named svnbackup, which is available from:
> 
> https://open.datacore.ch/read-only/svnbackup/trunk/
> 
> by svn and does exactly that. It dumps every revision commited to a 
> separate bzip2 compressed dump file in a configurable directory 
> structure. You can configure multiple repositories and then have 
> svnbackup backup all those  repositories in one go.

Dumping individual revisions is interesting, but a full backup every
period T is fine for the reasonable paranoid.  It could be a bit more
convenient when restoring too.

Anyway, for the less paranoid among us, hot-backup does the job.  The
less paranoid would be defined as the people who feel comfortable that
Berkeley DB 4.0 is a stable product (which given it's widespread use
wouldn't be that odd).

Above text is in no way meant to discourage people from looking at
Amirs svn tools BTW.  I haven't tried them.  I'm merely stating
what I know works.


Sander