Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bu.edu!transfer!ceylon!newshost!fn00 From: fn00@gte.com (Farshad Nayeri) Newsgroups: comp.unix.bsd Subject: Re: version control with 386bsd Message-ID: <FN00.92Sep16155157@tahoe.gte.com> Date: 16 Sep 92 19:51:57 GMT References: <cproto.716644144@marsh> Sender: news@ceylon.gte.com Organization: GTE Laboratories, Waltham, Massachusetts, USA Lines: 36 In-reply-to: cproto@cs.curtin.edu.au's message of 16 Sep 92 11:49:04 GMT In article <cproto.716644144@marsh> cproto@cs.curtin.edu.au (Computer Protocol) writes: Take the kernel for example. If you have all kernel sources under RCS control then you have to either check out all sources and include files required for a later make or you have to add some rules to the makefile to check out required sources and remove them after the compilation. The second option doesn't work for include files or if explicit rules are specified for a certain target. The first option has the drawback that after the make you have to remove all sources and includes. Another possibility is to edit all required makefiles to do all individual checking out and remove all sources once they are not required any further. (YUCK) Note that if you check out all required sources for a large make then you require twice the diskspace occupied by your sources. If you use CVS you again have no option but to check out all files in advance before you start your make. Could it be that i'm blind and don't see the obvious solution? I think GNU Make takes care of this by automatically checking out files before compiling, and removing them after it is done. I don't know if anyone has ported GNU Make to 386BSD and/or if there are Makefile portability problems between BSD and GNU. --farshad -- -- Farshad Nayeri Intelligent Database Systems fn00@gte.com Computer and Intelligent Systems Laboratory (617)466-2473 GTE Laboratories, Waltham, MA "Our research shows that even double-clicking can be hard concept for some new users to grasp." -- John Cook, Apple consumer product manager