Date: Sun, 27 Dec 1998 03:21:38 -0800 From: Mike Smith <mike@smith.net.au> To: "Kaleb S. KEITHLEY" <kaleb@ics.com> Cc: hackers@FreeBSD.ORG Subject: Re: split scontrib, was Re: /usr/src/gnu sources Message-ID: <199812271121.DAA02164@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 27 Dec 1998 07:43:28 EST." <36862B70.2781E494@ics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > I couldn't find this in the FAQ or Handbook. What am I supposed to do > > > for the real sources? > > > > > > > No; if you're looking for where all the 'meat' is, see /usr/src/contrib; > > Eek. That's a shitload of stuff to download over my pitiful 28.8 line -- > just so I can look at binutils/ld sources. You don't track the repository? Go to ftp.freebsd.org and get the relevant subdirectories (it'll tar them up for you...) > May I suggest that the toolchain be split out of scontrib? That's still > not optimal because the gcc part of the toolchain is huge, but it'd be > better than being forced to get sources for things like awk, amd, bind, > and a whole slew of other things I'm (and perhaps other people are) not > interested in. (Might be the person who wants bind/named sources doesn't > want to be forced to get the gcc sources?) > > Perhaps stoolchgcc, stoolchmisc, and scontrib with everything that's not > in stoolchgcc and stoolchmisc? Breaking the directories doesn't make any sense; any method of fetching them already has better granularity (except perhaps CVSup). If you want smaller CVSup fragments, talk to John. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812271121.DAA02164>