From: Chris Wright <chrisw@osdl.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Chris Wright <chrisw@osdl.org>,
Kay Sievers <kay.sievers@vrfy.org>,
git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] add git.spec and adapt Makefile for RPM build
Date: Mon, 2 May 2005 12:08:52 -0700 [thread overview]
Message-ID: <20050502190852.GH18917@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200505021858.j42Iw4M1029427@laptop11.inf.utfsm.cl>
* Horst von Brand (vonbrand@inf.utfsm.cl) wrote:
> Chris Wright <chrisw@osdl.org> said:
> > It simply means a structured release process. IOW,
> > the git.spec would be generated for a release tarball.
>
> Come on, you have to fix the spec file for the changelog and version by
> hand anyway, autoconfiscating it doesn't help one iota there.
That's the point, you don't _have_ to do that.
> And yes, I've seen quite a few packages autogenerating the spec file. As a
> result, you /can't/ build the package from pristine sources, you have to
> unpack and configure to get enough for building. For me that just isn't
> acceptable, as it completely misses the point of RPM.
>
> (You can go "rpmbuild -ta whatever-2.3.1.tar.bz2" if the tarball is set up
> correctly, your idea prevents that).
You just place the generated spec file in a release tarball. IOW, your
'release' Makefile target depends on foo.spec, and creates a clean release
tarball with all you need to do an -ta build.
thanks,
-chris
prev parent reply other threads:[~2005-05-02 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 10:23 [PATCH] add git.spec and adapt Makefile for RPM build Kay Sievers
2005-05-02 14:52 ` Kay Sievers
2005-05-02 17:41 ` Horst von Brand
2005-05-02 18:39 ` Chris Wright
2005-05-02 18:58 ` Horst von Brand
2005-05-02 19:06 ` Paul Jakma
2005-05-02 19:13 ` Paul Jakma
2005-05-02 19:08 ` Chris Wright [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050502190852.GH18917@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=torvalds@osdl.org \
--cc=vonbrand@inf.utfsm.cl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.