[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: FW: Subversion 1.0.1 Win32 version

From: Perry E. Metzger <perry_at_piermont.com>
Date: 2004-03-25 16:50:18 CET

kfogel@collab.net writes:
> "Perry E. Metzger" <perry@piermont.com> writes:
>> In the NetBSD project, we have set up an automated build system for
>> binaries, so when we do a branch or tag, or even just day to day,
>> people can always get fresh binaries. I'd happily help with such a
>> thing for Subversion.
> That's a very welcome offer! Could you help organizationally as well
> as technically?

I actually can help organizationally far better than I can
technically. I don't actually understand all the build issues on all
platforms, but I am willing to organize things and try to do my best
to provide a unified framework for doing builds.

> It'd be *great* to have binary builds be an automatic part of the
> release process, but just haven't had time to work much on it. If
> there were some arrangement whereby we could just hand The System a
> source tarball and get the appropriate set of binaries out, that would
> be a huge win. "The System" would be some combination of human and
> automated processes -- of course I'm not expecting a total lack of
> human involvement, but the more automated, the better.

Indeed. Ideally, people could volunteer their hardware and not
actually have to do more than setting up some sort of cron job or
something similar.

> Organizationally, what's needed is someone to come up with a list of
> the platforms we do binaries for, then match those with volunteers
> equipped to produce the binaries.

Right now, we seem to have the following sets of platforms listed on
the web site. (I've also listed the apparent build master...)

Red Hat: David Summers

        Distribution Mechanism: RPMs for download

        Redhat 7.X (i386)
        Redhat 8.0 (i386)
        Redhat 9.0 (i386)
        Fedora Core 1 (i386)
        WhiteBox Enterprise Linux 3 / RedHat Enterprise Linux 3 (i386)

Debian GNU/Linux: David Kimdon

        Distribution Mechanism: apt-get

        Debian Unstable "Sid" (what platforms?)
        Debian Stable "Woody" (what platforms?)

SuSE Linux: Olaf Hering

        Distribution Mechanism: RPMs for download

        What versions/platforms?

FreeBSD: Lev Serebryakov

        Distribution Mechanism: "ports" system

NetBSD: Eric Gillespie

        Distribution Mechanism: "pkgsrc" system

Mac OS X: Christian Schaffner

        Distribution Mechanism: Fink

Win32: Branko Cibej + Jostein Andersen

        Distribution Mechanism: zip files for download/self
                installing exe for download.

I've seen mentions of several other platforms of late, though, that
aren't on the official download list, including Mandrake.

BTW, whatever mechanism we pick, we should probably start digitally
signing "official" packages being distributed via the subversion
download area to prevent possible distribution of trojaned binaries.

> (IMHO, it'd be good for this to be completely separate from the
> Release Management process. RM is just about getting the vetted
> source tarball out the door. Binaries are about turning that source
> into executables. Best to distribute the load and not burden the RM
> with additional responsibilities, when a clean separation is
> possible.)

That seems reasonable.

> I wasn't sure if you meant you could volunteer to produce binaries for
> some platforms, or to help organize a general binary producing effort,
> or both.

I can't really volunteer for terribly many platforms -- I don't
possess many. However, I'm willing to take ownership of the overall
problem, at least for a time, if that will help.

Perry E. Metzger		perry@piermont.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 16:50:52 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.