I am definitely interested. :) Since I didn't realize there was someone to turn to
enable me to compile Mandrake RPMS. Plus w/ the changes I've got here, it should be
easier to put into cooker since it will already auto-conform.
Right now, I am updating some of the constructs in the mandrake9.1 subdirectory to
no longer patch build-outputs.mk, since if the autodependency order changes, the
patch is invalid - plus we shouldn't be patching a generated file if we can help it.
I have also made a few changes which no longer require ~/.rpmmacros and ~/.rpmrc to
be created and can use a stock Mandrake system to build the rpms for any user -
using root configuration for the root user and a generic one for regular users.
I believe the same can be said for the 9.0.
I have added the ability to indicate whether dependencies should be checked by rpm
when building.
I have also corrected the neon dependency by allowing the user to define in the
Makefile what the version of neon should be and propagated it to BuildRequires.
I have also corrected the BuildRequires to list krb5-devel - which is required and
causes the build to fail if it is missing.
I have also corrected the BuildRequires to list the most up to date version of the
libdb4.x library which is available on the system on which it is being built,
defauilting to the db4.0 version if none is present.
Still working on getting the build-outputs.mk translation correct. Almost there. The
other parts work like a charm.
Shamim Islam
Michael Ballbach (ballbach@rten.net) wrote:
>
>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.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 17 20:34:05 2003