From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Distribution making |
Date: | 2000-07-11 16:22:30 |
Message-ID: | Pine.LNX.3.96.1000711180404.17539A-100000@ara.zf.jcu.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 11 Jul 2000, Lamar Owen wrote:
> > IMHO to *source* tree belong to matter for binary making only. A
> > distribution must be out of source.
>
> There are more files in the RPM set, for instance, than just the
> binaries -- there is the spec file, which controls the building of the
> RPM's; there is a patch file (to patch around some madness in the source
> that breaks the RPM package in some way); there are a couple of scripts
> (startup and upgrade); there is a man page for the upgrade script; as
> well as other things. Now, getting the *source* of the RPM distribution
> packaging into the tarball might be OK -- I'm certainly not advocating
> packaging binaries in the tarball!
I good known how act RH packaging. And I probably understant you.
> Therefore, a separate source RPM would not need to be distributed -- a
> person can just download the tarball, execute a single command, and have
> properly built RPM's for their system ready to install. Can't get much
> easier than that!
Yes, I know. But it expect that in the *common-original-source* must be
.spec file. Or not?
I'm not enemy of RH, I only not sure if is good "foul" original source.
Karel
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-07-11 16:32:16 | Re: md5 again |
Previous Message | Tom Lane | 2000-07-11 16:13:57 | Re: fmgr changes not yet ported to AIX |