packaging (was: Re: Mandrake 9.0 RPMS)

[Greg Stein <gs...@lyra.org>]

On Tue, Oct 15, 2002 at 11:27:17AM -0600, Michael Ballbach wrote:
>...
> I've made some mandrake 9 rpms to facilitate installing subversion and
> related bits. The url is http://www.rten.net/mdk-svn.html

Cool.

>...
> The apache2 rpm is just a rebuild of the cooker apache2 with DB4 and
> maintainer mode. The swig rpm is a rebuild with the more recent swig.
> neon, db4, and subversion were built with new spec files. I didn't
> notice the subversion redhat spec until I was partly through writing the
> mandrake spec, but when I did notice it I tried to make them more or
> less match with their output. I did not, however, separate cvs2svn off
> into its own rpm. I included the python bindings and the script in the
> main rpm.

I would think that users will want several RPMs. Something like:

* subversion-base
* subversion-client
* subversion-server
* subversion-devel
* subversion-python

If we say that the server cannot be installed without the client, then the
-base can disappear. Note that we can also separate the client into several
pieces if we want:

* subversion-client-common
* subversion-client-dav
* subversion-client-local

We've architected the RA layer to detect and load RA backends, so we don't
necessarily have to have both at the same time. Note that -local would
depend upon DB4, while -dav would depend on Neon.

The last bit of granularity, and possible resolution would be the dependency
handling for DB4. -local and -server both depend upon it, and the libraries
they install, too. So you might have something like subversion-repos.

Now... I don't know about doing this many RPMs. I can definitely see the
Debian folks doing this, as they like to have fine-grained dependencies. The
dependency tree would be something like:

  subversion-base
    subversion-client-common
      subversion-client-dav (also on Neon)
    subversion-repos (also on DB4)
      subversion-server (also on apache2)
      subversion-client-local (also on -client-common)
    subversion-devel
    subversion-python (also on swig (runtime))

Urf. Would -devel or -python need to be split, too? Oy... :-)

> The source rpms and some convenience archives are up there too.
> Hopefully, as the spec file matures for the subversion portion, it or a
> derivative can be incorporated into packages/rpm/mandrake-9 or similar.

If I gave you commit privs, would you be willing to maintain your .spec file
and other build bits in the a new /trunk/packages/mandrake section?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: packaging (was: Re: Mandrake 9.0 RPMS)

[Michael Ballbach <ba...@rten.net>]

On Tue, Oct 15, 2002 at 12:27:03PM -0700, Greg Stein wrote:
> I would think that users will want several RPMs. Something like:
> 
> * subversion-base
> * subversion-client
> * subversion-server
> * subversion-devel
> * subversion-python
> 
> If we say that the server cannot be installed without the client, then the
> -base can disappear. Note that we can also separate the client into several
> pieces if we want:
> 
> * subversion-client-common
> * subversion-client-dav
> * subversion-client-local
> 
> We've architected the RA layer to detect and load RA backends, so we don't
> necessarily have to have both at the same time. Note that -local would
> depend upon DB4, while -dav would depend on Neon.
> 
> The last bit of granularity, and possible resolution would be the dependency
> handling for DB4. -local and -server both depend upon it, and the libraries
> they install, too. So you might have something like subversion-repos.
> 
> Now... I don't know about doing this many RPMs. I can definitely see the
> Debian folks doing this, as they like to have fine-grained dependencies. The
> dependency tree would be something like:
> 
>   subversion-base
>     subversion-client-common
>       subversion-client-dav (also on Neon)
>     subversion-repos (also on DB4)
>       subversion-server (also on apache2)
>       subversion-client-local (also on -client-common)
>     subversion-devel
>     subversion-python (also on swig (runtime))
> 
> Urf. Would -devel or -python need to be split, too? Oy... :-)

I agree - certainly it needs to be relatively fine grained, and I didn't
like that I put the python stuff in the main RPM. I've changed the spec
file to follow the tree you've laid out, and am working on building a
new set of mandrake rpms right now, if they come out okay I'll post them
within a day or so.

> If I gave you commit privs, would you be willing to maintain your .spec file
> and other build bits in the a new /trunk/packages/mandrake section?

I'd be happy to.

-- 
Michael Ballbach, N0ZTQ
ballbach@rten.net -- PGP KeyID: 0xA05D5555
http://www.rten.net/