Re: Call for developers: rpmbuilder

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



So, this tool looks promising to my employer.  What sort of help do you
need?

Don

On Tue, Sep 09, 2008 at 02:01:33PM -0400, Chris Evich wrote to To fedora-devel-list@xxxxxxxxxx:
> > On Mon, Sep 8, 2008 at 1:30 PM, Chris Evich <cevich redhat com> wrote:
> >> Hi,

> >> Hopefully this is the right mailing list :)

> >> Project rpmbuilder aims to provide a template-based approach to packaging.  In
> >> other words, it removes responsibility from developer to produce an RPM spec
> >> file the "right" way.  Instead, the package developer just feeds in his
> >> project's particulars, and a template-driven engine puts the pieces together
> >> and spits out a "sane" RPM and SRPM.

> >> https://fedorahosted.org/rpmbuilder

> > Personally I would rather see Fedora heavily invest in reducing all
> > the overhead that currently exists in packaging and putting more
> > intelligence into the core of the system, rather than generating spec
> > files.  Editing spec files is already painful enough; editing
> > generated ones sounds even less fun.  Essentially if the build system
> > knows about things like the Ruby gem specs, Python setup.py, Java's
> > Maven, freedesktop.org autotools-based desktop packages, etc., then
> > you don't need to autogenerate a lot of spec boilerplate.


> Actually, I completely agree, and this project is intended to address the
> hand-editing you describe.  The templates rpmbuilder uses will be shipped
> _with it_, I'm not suggesting yet-another-thing-to-edit-when-packaging :)
> Then, different templates may be specified at packaging time depending on the
> "thing" to be packaged.

> For example, I could envision a template for packaging python "stuff" that
> uses a setup.py when resolving a python-rpmbuilder template.  In other words,
> it should be as simple as:

> # rpmbuilder --mode=python --pkgname=MyRPMPackageName
>  --version=1.2.3 --release=4 --sourcedir=. --destdir=.

> The result would be, ./MyRPMPackageName-1.2.4-4.noarch.rpm and/or
> ./MyRPMPackageName-1.2.4-4.noarch.srpm are written to CWD.

> Though this could easily extend to other scripting languages / build
> environments as well.  All that's needed is someone to develop a template once.
-- 
Don Harper, RHCE                                email: duck@xxxxxxxxxxxx
Just a systems kinda guy...                      http://www.duckland.org
        OK, the joke is over. Bring back the Constitution.
A good friend is a connection to life - a tie to the past, a road to the
         future, the key to sanity in a totally insane world. - Lois Wys

Attachment: pgpDAQSqyDdna.pgp
Description: PGP signature

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux