From: Paul Jakma <paul@clubi.ie>
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 20:06:50 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.62.0505022005200.14200@sheen.jakma.org> (raw)
In-Reply-To: <200505021858.j42Iw4M1029427@laptop11.inf.utfsm.cl>
On Mon, 2 May 2005, Horst von Brand wrote:
> 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.
I think maybe you're missing the point of what is sometimes known as
a 'make dist' target. (eg in autoconf type build systems).
> (You can go "rpmbuild -ta whatever-2.3.1.tar.bz2" if the tarball is set up
> correctly, your idea prevents that).
Then the tarball wasn't of distributable (ie end-user buildable)
source.
regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
Fortune:
"Now this is a totally brain damaged algorithm. Gag me with a smurfette."
-- P. Buhr, Computer Science 354
next prev parent reply other threads:[~2005-05-02 19:01 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 [this message]
2005-05-02 19:13 ` Paul Jakma
2005-05-02 19:08 ` Chris Wright
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=Pine.LNX.4.62.0505022005200.14200@sheen.jakma.org \
--to=paul@clubi.ie \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).