In theory you can put any binary files into Git, but people tend to avoid it since every clone of the repository will become quite large. I'd recommend only placing source code into the repository. Instead, host larger binary downloads like your bld-1.0.2.tar.xz files from some other location that's not a Git repository. Another possibility is to use GitHub's "Releases" feature, see here, I haven't tried it myself but it looks like you can attach binaries to releases. Note that since your current repo already includes the binary files in its history, the best way to get rid of them is to start a new repo with a clean history.

Also, I would recommend against putting other project's source trees into yours. You'll end up having to keep your repo up to date with the source repo all the time. Instead, look into externals (known as submodules in Git), see for example here. Another approach, useful for when the VCS systems aren't compatible, is to include in your project a script to download the other project's source code.

In reply to Re^3: 'bld' project - signature(SHA1) based replacement for 'make' by Anonymous Monk
in thread 'bld' project - signature(SHA1) based replacement for 'make' by rahogaboom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.