From owner-freebsd-hackers Fri Dec 23 13:36:44 1994 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA23073 for hackers-outgoing; Fri, 23 Dec 1994 13:36:44 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA23067 for ; Fri, 23 Dec 1994 21:36:43 GMT Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id NAA19940; Fri, 23 Dec 1994 13:35:45 -0800 X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol To: Mark Murray cc: hackers@freebsd.org, current@frreebsd.org Subject: Re: How much of a schlepp... In-reply-to: Your message of "Fri, 23 Dec 94 19:44:42 +0200." <199412231744.TAA15897@grunt.grondar.za> Date: Fri, 23 Dec 1994 13:35:45 -0800 Message-ID: <19939.788218545@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@freebsd.org Precedence: bulk If someone wants to package up sup in a more user-friendly package, I won't argue, I just don't have time right now myself. Ideally, there should be a `sup starter kit' that asks you where you want to put src, ports, which collections you want, and then generates a supfile for you. Now that'd be a concept! :-) Jordan > ... or bummer would it be to have sup "its very small" included in the > bindist; _then_ supping could be a part of the 'make' structure? > > ie cd /usr/src/bin;make sup;make clean;make.... > > If there are objections to putting _sup_ in by itself (I suspect there > may be), what about just putting some sup targets into the makefiles? > having an all-or-bust sup system is starting to make less sense at the > end of a slow wire. I am not referring to the one currently in > /usr/src/Makefile, but rather farming the individual lines in the > supfile out to their respective directories. > > How does it sound? > > M > > -- > Mark Murray > 46 Harvey Rd, Claremont, Cape Town 7700, South Africa > +27 21 61-3768 GMT+0200