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

Re: why patch build-outputs.mk in svn-install.patch WAS: Update packages/rpm/mandrake9.1/svn-install.patch

From: Michael Ballbach <ballbach_at_rten.net>
Date: 2003-09-17 20:13:36 CEST

On Wed, Sep 17, 2003 at 06:00:53PM +0000, Files wrote:
> You are wanting me to take over ownership of only the mandrake rpms
> correct?

I am not _wanting_ you to do anything, if you're interested then I would
be open to that, yes, assuming you have more time then I do and that you
have the skills necessary.

My overriding concern is that subversion has reasonable support for
building mandrake RPMs until the point that one appears in cooker and is
maintained by mandrake itself. If you are in a better position then I to
make sure that happens then that's great.

> How do we do something like that?

Well, I'd sort of like to see your changes first. I re-read the email
and got a little concerned when you mentioned bundling the .rpmrc and
.rpmmacros files. Those are individual preference files and they have
no place being bundled with any specific RPM specification.

They generally need some minimal content to generate RPMs for mandrake.
They can, however, have wildly different contents depending on the
builder of the RPM. Those instructions are meant as a very basic
introduction to the user that has never built RPMs before, and not the
be-all and end-all of how you should have your rpm build environment set
up.

Whatever other changes you have, I'd still like to see.

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

  • application/pgp-signature attachment: stored
Received on Wed Sep 17 20:14:22 2003

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

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