1. 12 Apr, 2013 3 commits
  2. 26 Mar, 2013 1 commit
  3. 11 Mar, 2013 2 commits
  4. 05 Mar, 2013 2 commits
  5. 02 Mar, 2013 2 commits
  6. 27 Feb, 2013 1 commit
  7. 26 Jan, 2013 1 commit
  8. 01 Dec, 2012 1 commit
  9. 12 Nov, 2012 1 commit
  10. 07 Nov, 2012 1 commit
  11. 11 Oct, 2012 1 commit
  12. 10 Oct, 2012 2 commits
  13. 09 Oct, 2012 1 commit
  14. 08 Oct, 2012 2 commits
  15. 03 Oct, 2012 2 commits
  16. 02 Oct, 2012 1 commit
  17. 30 Sep, 2012 2 commits
  18. 28 Sep, 2012 3 commits
  19. 26 Sep, 2012 2 commits
  20. 19 Sep, 2012 1 commit
  21. 29 Aug, 2012 1 commit
  22. 17 Aug, 2012 1 commit
  23. 14 Aug, 2012 1 commit
  24. 11 Aug, 2012 2 commits
  25. 01 Aug, 2012 2 commits
    • Place the freshly built RPM directly into rpm-build/ · 6b774f8c
      So we get the exact behavior as the SRPM build
      Dag Wieërs committed
    • Implements git commit date into RPM release · ec7c8eb8
      With this patch one can do `make rpm` and get an RPM file that looks like:
      
        rpm-build/noarch/ansible-0.6-0.git201208010541.el6.noarch.rpm
      
      My goal was not to rewrite the original SPEC file, and/or the tarball. In other
      projects what I tend to do is prepare the SPEC file in the tarball with the
      correct version/release so that rpmbuild works on the (released) tarball as
      well. If this is wanted, we will have to rewrite the SPEC file on the fly as
      part of creating the tarball. If there is no git or .git/ available, we will
      use the current time.
      Dag Wieërs committed
  26. 24 Jul, 2012 1 commit