httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Kraemer <martin.krae...@mch.sni.de>
Subject Re: Binary tarballs
Date Thu, 08 Oct 1998 19:31:50 GMT
On Thu, Oct 08, 1998 at 09:29:48AM -0400, Jim Jagielski wrote:
> 
> I think that including source is in keeping with the spirit of
> Open Source. Also, it allows those with binary builds to change it
> as needed without needing to download the source.

Okay. Then let me add something like the following as a 4th proposal
to the STATUS file:

      4. A "binary release" tarball (as noted under 2.) with the
	 addition of the _compressed_ source archive from which the
	 binary was produced. After unpacking the binary tar file
	 (which must of course contain the directory paths except for
	 the top level (rootdirectory) slash; btw. gnu tar strips off
	 this slash by default), the administrator has the chance to
	 remove this source archive to save space, or keep it in
	 place for later possible use. An example tar contents could
	 start like this:
	 drwxrwxr-x  0/0     0 Jul 17 10:59 1998 usr/local/apache/
	 drwxr-xr-x  0/0     0 Oct  7 13:13 1998 usr/local/apache/src/
	 drwxr-xr-x  0/0     0 Oct  7 13:13 1998 usr/local/apache/src/apache_1.3.3.tar.gz
	 drwxr-xr-x  0/0     0 Oct  7 13:13 1998 usr/local/apache/conf/
	 -rw-r--r--  0/0 12415 Oct  7 13:13 1998 usr/local/apache/conf/httpd.conf.default
	 lrwxrwxrwx  0/0    15 Aug 22 10:14 1997 usr/local/apache/conf/httpd.conf
	 -rw-r--r--  0/0  2842 Oct  7 13:13 1998 usr/local/apache/conf/access.conf.default
	 -rw-r--r--  0/0     0 Jul 20 13:46 1998 usr/local/apache/conf/access.conf
	 ...
	 Note that compressing such a tar file will not gain much
	 space, because the sources have been compressed already.


    Martin

Mime
View raw message