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

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • 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 also makes it easy to ditch all the build-related history: just kill that branch.

    • 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