Date: 28 Oct 1996 09:33:01 -0800 From: jdp@polstra.com (John Polstra) To: freebsd-current@freebsd.org Subject: Re: -current failed Message-ID: <552qod$rqk@austin.polstra.com> References: <2690.846506856@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <2690.846506856@time.cdrom.com>, Jordan K. Hubbard <jkh@time.cdrom.com> wrote: > > Sup works just fine. The last, and only, time I looked into cvsup, > > I needed to install a >50Mbyte modula-3 port. This is not a good > > But you don't. Install the package at ftp://freefall.freebsd.org/pub/CVSup I am planning to make the entire situation regarding CVSup and Modula-3 a lot better this week. I am splitting the Modula-3 port into two pieces: "modula-3-lib" and "modula-3". The former will install _only_ the shared libraries for the runtime system. It uses a couple megabytes of disk space, if I remember correctly. The package itself (the .tgz file) is around 1 MB. I am changing the dependencies for the CVSup port so that it depends on "modula-3-lib" rather than "modula-3". People who install the CVSup package will also get the "modula-3-lib" package, but not all the other Modula-3 stuff. People who want the whole Modula-3 development system can still install the "modula-3" port/package and get it all. Here's a picture. "--->" means "depends on": cvsup ----------> modula-3-lib ^ | modula-3 ---------+ I think this new setup will address the complaints about the hassle of using Modula-3. I had hoped that the static CVSup binaries would accomplish that but they haven't. Too many people forget about them, or never find out about them, or just don't like the idea of them. Also coming Real Soon Now is SOCKS support. Keep those suggestions coming! John "All Ears" Polstra -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?552qod$rqk>