Call for input: customer contributed RPMS in the unofficial repository

Todd Lyons tlyons at
Wed Jun 6 18:01:44 CDT 2007

Hash: SHA1

On Thu, May 31, 2007 at 01:16:47PM -0500, Michael E Brown wrote:

>On Thu, May 31, 2007 at 07:04:44PM +0100, Hostmaster wrote:
>> Fabulous Idea!
>> However, may I suggest something such as a CVS? Scripts and packages could then
>> be manageably improved over time by multiple people.
>We have public git repositories available (
>They are currently read-only, but I have a few ideas for how to make
>them read/write. Most probably anything I set up would be based upon git

You should recommend to rpm builders that they look into mezzanine for
local rpm package management.  It makes building rpms a piece of cake.
If the builder chooses to use a local cvs, patch management versioning
becomes simple as well.

Common commands:
mzimport (to import a src rpm into basic directory structure)
mzprep (to build a "work" area that you can manually edit files for
        the purpose of creating patches)
mzpatch (create said patches)
mzbuild (build the rpms)

It can do much more than this, but these are the basic functions.
- -- 
Regards...		Todd
When engineers want simple solutions to complicated social problems,
freedom is the first victim...                      --Stephane Bortzmeyer
Linux kernel 2.6.17-6mdv   1 user,  load average: 0.07, 0.04, 0.05
Version: GnuPG v1.4.7 (GNU/Linux)


More information about the Linux-PowerEdge mailing list