Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Thinking of tracking build artifacts in git More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Workflow (Score:1)

by Aristotle (5147)

I think I would try keeping the artefacts in a different branch, putting a different .gitignore in each branch. When you want to build, you check out the build branch, merge the source branch, build, and commit. To resume developing, you check out the source branch again.

I haven’t thought through all the consequences, but I think that would be a fairly practicable way of keeping binaries around without mixing the build-related history and the source-edit-related history into a giant mishmash. It als
- Re:Workflow (Score:2)
  
  by jdavidb (1361) on 2008.05.16 8:41 (#62892) Homepage Journal
  
  Thanks for the suggestion! I will add this to my musings over the next few days. :)
  
  --
  J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.