NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/os/linux/9946

Text File | 1992-09-07 | 1.6 KB | 43 lines

Newsgroups: comp.os.linux
Path: sparky!uunet!mcsun!sun4nl!dutrun!donau!hal.et.tudelft.nl!wolff
From: [e-mail] (Rogier Wolff)
Subject: Distribution sugestion for gcc.
Message-ID: <[e-mail]>
Sender: [e-mail] (UseNet News System)
Nntp-Posting-Host: hal.et.tudelft.nl
Organization: Delft University of Technology, Dept. of Electrical Engineering
Date: Sat, 05 Sep 1992 17:03:44 GMT
Lines: 31

Hi,

I have been thinking about the method gcc is being distributed.
(partly because I had problems myself, and I seem to be not the only
one)

Anyway, how about creating a tar file with EVERYTHING in it. This could
be done in two ways:
1)   all the files that are in there now + an install script.
2)   ALL that gcc needs. Even the links etc that the install script makes.

Option one simply guarantees that you have all the files necessary.
Option two even eliminates the install script. (Tar should be capable
of tarring and restoring symlinks and hardlinks. right?)

Now by this time everybody will be screaming that this will result in
a very large file. This can be accomodated by providing two versions:
one in a large file. The second split into chunks of about 1.2 megabytes.
People can then split the large file into pieces if they want, or
keep it in one chunk if possible. The smaller files can easily be transported
on floppies.

--
Ok. Suggestions? pro's con's?

                    Roger.

--
If the opposite of "pro" is "con", what is the opposite of "progress"?
(stolen from  [e-mail], who got it from [e-mail])
EMail:  [e-mail]   ** Tel  [phone] or [phone]