Re: RFC gawk update

[Jeremy Messenger <mezz7@xxxxxxx>]

On Mon, 01 Mar 2004 22:43:19 -0800, Chris Pressey wrote:

> On Mon, 01 Mar 2004 21:47:40 +0000
> skrueger@xxxxxxxxxx wrote:
> 
>> hi folks,
>> 
>> I've "imported" gawk-3.1.3, you can find all files on
>> http://tecneeq.dyndns.org/~cosmicdj/DragonFly/
>> 
>> contrib_gawk-3.1.3.tar.bz2 goes into /usr/src/contrib
>> gnu_usr.bin_gawk.tar.bz2 goes into /usr/src/gnu/usr.bin
>> 
>> gnu_usr.bin_Makefile.patch.bz2 is for /usr/src/gnu/usr.bin/Makefile not
>> needed right now unless you want to buildworld!!!
>> 
>> sadly gawk's info doesn't work with our (aged) texinfo, so the build
>> will fail in gawk/doc :-(
>> 
>> I plan to update texinfo tomorow if no one objects
>> 
>> comments? objections? flames? ;-)

What's wrong with the awk one in the base system? gawk should be part of
package; not in the base system since we already have one. No need to add
the more of junk in the base system when most of people are trying to get
rid of junk and turn them into package.

BTW: Last time I checked, awk is faster, smaller and has lesser bugs than
gawk.

Cheers,
Mezz

> Only one:
> 
> Submissions should probably go to submit@xxxxxxxxxxxxxxxxxxxxxxx, not
> commits@ (which is primarily for commit messages from CVS)
> 
> Other than that... sorry, I don't know what to make of it yet :)
> 
> We could really use an official statement/HOWTO of the preferred method
> for putting contrib/gnu/vendor branches in the tree... stated on the
> webpage or somewhere... I know it involves putting the contrib in
> verbatim, and using patches to generate the DFly-specific version before
> the build, but I don't know the mechanics yet.
> 
> I assume this (gawk submission) complies with the general idea, but I'll
> have to do some digging to find out for sure.
> 
> -Chris
> 
>> PS: still this has to survive a full buildworld which I'll do after the
>>     texinfo update
>> 
>> PPS: could someone tell me what files to delete from vendor source
>> packets
>>      and which files (besides source need to compile) should stay?
>> 
>> regards,
>> SK


-- 
bsdforums.org 's moderator, mezz.