1. 22 Sep, 2011 5 commits
    • Michael Pyne's avatar
      Tag kdesrc-build 1.14.1 · 808bb522
      Michael Pyne authored
    • Michael Pyne's avatar
      Partially revert --delete-my-patches, implement correctly. · b094318f
      Michael Pyne authored
      I just rediscovered why having singular options that don't accept
      values, and combining those with extract_option_value(), is a bad idea
      (Hint: It removes the command line entry following the option in
    • Michael Pyne's avatar
      Allow kdesrc-build to remove existing source dirs. · a28539a2
      Michael Pyne authored
      That is, if the user permits it using --delete-my-patches, and only for
      git clones at this point.
      This should hopefully resolve bug 282367 (also frequently reported on
      IRC ;)
    • Michael Pyne's avatar
      Add --delete-my-patches option. · cd4bafc2
      Michael Pyne authored
      This doesn't so much actively search for things to delete. Instead it's
      a required permission from the user to remove source directories (which
      is similar to the remove-after-install option).
      Right now this will only be used when trying to clone a git module and
      the destination source directory already exists somehow, which has
      happened for a lot of 1.14 early adopters due to old kde-baseapps
      checkouts having a kate or konsole directory that conflict with where
      kdesrc-build wants to put the current kate/konsole directories.
    • Michael Pyne's avatar
      kdesrc-build: Prefer module type to on-disk info. · cd4090b1
      Michael Pyne authored
      This commit makes the "module type" as determined from the
      {repository,svn-server} options be the preferred method of determining
      which scm tool to use.
      This is required to allow nuking the source directory for old checkouts
      in an upcoming commit (which was itself made an issue with the 1.14
      release, that reorganized the on-disk layout, causing older kde-baseapps
      checkouts with konsole/kate subdirs to conflict with the git
  2. 21 Sep, 2011 1 commit
  3. 20 Sep, 2011 1 commit
  4. 19 Sep, 2011 3 commits
  5. 18 Sep, 2011 3 commits
  6. 17 Sep, 2011 1 commit
  7. 14 Sep, 2011 1 commit
    • Michael Pyne's avatar
      Use more "standard" Perl for kde: auto-handling. · 737484c8
      Michael Pyne authored
      Laurent Montel reported an error that indicates a syntax error in the
      git error handler for the kde: support. Even after extracting out the
      error handler and forcing it to run Perl works just fine here, so it's
      not a semantic issue either.
      So instead, just use a plain 'ol Perl 5.0-style hash to figure out the
      error message, no need to make it complicated.
      In addition I added the stderr > /dev/null redirection that I forgot to
      have in place before.
  8. 12 Sep, 2011 4 commits
  9. 11 Sep, 2011 2 commits
    • Michael Pyne's avatar
      Add a man page for kdesrc-build. · a7039704
      Michael Pyne authored
      I probably should have done this a long time ago, but now kdesrc-build
      has a man page (mostly to get rid of the 1 Debian lintian hit I saw for
      I haven't tied it into CMake yet because I'm tired, but it requires
      asciidoc and the short story is:
      $ asciidoc -d manpage -b docbook kdesrc-build.1.txt
      $ xsltproc --nonet /usr/share/asciidoc/docbook-xsl/manpage.xsl
      Of course finding that damn XSL from CMake will be the problem in the
      future but I can figure that out tomorrow if no other kind soul does
      that for me.
    • Michael Pyne's avatar
      Bugfix: Handle set-env in module-set correctly. · 8841e085
      Michael Pyne authored
      Raphael Kubo da Costa noticed that his set-env in module-sets were no
      longer working in master.
      Turns out a simplification of the setOption method to allow accepting
      more than one option did not properly handle the set-env option if that
      option had already been processed. (kdesrc-build has to convert set-env
      read from the rc file into a hash instead of just storing the value to
      allow for duplicate set-env entries).
      This is fixed by ensuring that if that processing step has apparently
      already been completed, we don't try doing it again.
  10. 10 Sep, 2011 8 commits
  11. 08 Sep, 2011 4 commits
  12. 07 Sep, 2011 7 commits