Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
There are certainly arguments both ways.. But for quality control purposes it might make a lot of sense to store your released files in your SCCS. -derek Quoting Stephen Adler <adler at stephenadler.com>: > Guys, > > I'm setting up a new repository for a business I'm consulting for. > They are currently a clear case house. > One thing which I've noticed is that they store all output file from > the build into their clearcase repository. > This goes against my philosophy that the only thing which goes into a > source code repository are the files > which are needed to build the executables, and not the executables > themselves. Now I'm having > seconds thoughts about my "what gets stored in a source code > repository" philosophy. Can anyone > comment on whether its custom to archive the executables as well? One > issue is that I'm working > under a quality system so control of files is required. I supposed > this meant control of source files, > but perhaps control of derived binaries from the source files is also > required? > > As usual, all comments are greatly appreciated. > > Cheers. Steve. > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://olduvai.blu.org/mailman/listinfo/discuss > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |