home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!news.service.uci.edu!ucivax!ucla-cs!ucla-mic!unixg.ubc.ca!unixg.ubc.ca!usenet
- From: gobbi@gdss.commerce.ubc.ca (Michael Gobbi)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: Project builder and source code control.
- Date: 17 Dec 1992 17:32:01 GMT
- Organization: The University of British Columbia
- Lines: 31
- Message-ID: <1gqdihINN3gq@iskut.ucs.ubc.ca>
- References: <1992Dec16.163137.5670@infotec.ch>
- NNTP-Posting-Host: gdss.commerce.ubc.ca
-
- In article <1992Dec16.163137.5670@infotec.ch> guy@infotec.ch (Guy Roberts)
- writes:
- > Two of us here are using the same Project Builder directory.
- > Now that nib files are directories, how are other developers
- > managing to stop people changing the same nib at the same
- > time and overwriting changes ? If the project was all made
- > up of flat files this would be possible with SCCS.
- >
- > I have not so far seen much about source code control in
- > the NeXT documentation. Is the idea that each developer
- > sticks to a discrete sub project ?
- >
- > Any ideas ?
- >
-
- The simplest solution that I can think of is to create a project account.
- People can copy out code and work on it within their own accounts, but
- must log in as the "project user" to copy the stuff back and remake the
- project.
-
- Another (dangerous) solution is to make ProjectBuilder and
- InterfaceBuilder into setuid programs.
-
- Both of these are workarounds to the real problem -- the fact that
- regardless of permissions, project builder refuses to modify certain files
- unless you are the owner. With any luck it will be solved in 3.1.
-
- --
- __ In quest of knowledge...
- /..\ <gobbi@gdss.commerce.ubc.ca>
- ---mm--mm---------------------------------------
-