Date: Sun, 3 Aug 1997 22:35:44 +0200 (MEST) From: Søren Schmidt <sos@sos.freebsd.dk> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: davidn@unique.usn.blaze.net.au, current@FreeBSD.ORG Subject: Re: ports-current/packages-current discontinued Message-ID: <199708032035.WAA03286@sos.freebsd.dk> In-Reply-To: <17040.870566767@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 2, 97 05:06:07 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Jordan K. Hubbard who wrote:
> [Trimmed to -current - PLEASE watch those cc lines, folks! We're all
> getting unforgivably sloppy here]
>
> > What features in tcl8.0 are required for a running FreeBSD system?
> > Why is it essential that tcl be present in the base system AT ALL?
> > What benefits are there in tcl being present here instead of being
> > built by the ports/packages system?
>
> OK, these are all good questions. I will attempt to answer some
> of them.
>
> 1. TCL needs, *at some point* (and note that the current move was
> rather premature, but let's not debate that here) to be part of
> the base system so that the installation tools can use it.
> We do intend on being heavy users of TCL, if not right this minute
> then in the future.
>
> 2. If it were in ports, we'd have a build problem since you wouldn't
> be able to build /usr/src/usr.sbin/setup (not existant yet, but
> it will be) without first building and installing a port. This
> would break the world target.
Wrong/bad arguments!
Setup belongs in release/ which is not build by default anyways, and
only has interest for people building their own releases.
You can move release/ off to ports or whatever for all I care, those
interested in building a release will also know howto get the tools
etc for it (if not, let them die silently :) )
This stuff is NOT needed for normal system use, just during install.
And for the libs, build setup statically :)
So the reason for bringing in TCL is invalid..
(almost the same applies to perl)
> Those are the questions which *must* be answered, and answered well,
> before we can start truly pushing things out of /usr/src and
> exclusively into the ports collection. Elitist solutions which
> require dedicated network access or more than a jellybean 486 (of
> which we still have many in our userbase) need not apply.
If they can afford to pull down the (by then) HUGE base system,
they could also afford to pull down the needed packages, in fact
that would need alot less space...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708032035.WAA03286>