1. 14 Feb, 2011 4 commits
    • Michael Pyne's avatar
      Make unknown command-line modules an error. · cf469049
      Michael Pyne authored
      It used to be that unknown modules would simply be attempted to build
      anyways, and it would be amusing if it failed, but with the new method
      of handling regular and XML-based modules, an unknown module simply
      causes no output and a successful return message.
      Now it results in an exception being thrown.
    • Michael Pyne's avatar
      Make it very clear use-xml-modules is gone. · 85c8b4f2
      Michael Pyne authored
      This should help people testing trunk fix their configs before the
      eventual release. ;)
    • Michael Pyne's avatar
      Revert auto-guessing of repository URLs. · 6ad18d07
      Michael Pyne authored
      Basically, nothing good can come of more auto-guessing of this style.
      dfaure has encountered issues with it, and I've run into a few yourself.
      Just specify the right repository (and you should be using module-sets
      by now anyways) and we'll all be OK. ;)
    • Michael Pyne's avatar
      Replace use-xml-modules with repository overload. · a12e84d8
      Michael Pyne authored
      Having use-modules and use-xml-modules is stupid.
      Instead, you can use "kde-projects" for the existing repository option
      to allow kdesrc-build to know that you mean for the module to be built
      based on the KDE Projects structure, and kdesrc-build will handle the
      rest, and then use use-modules as normal.
      This means that you can't mix XML-based modules and the old-style
      modules in the same module-set, but oh well...
      You can still use +-prefixed module identifiers on the command line as
  2. 11 Feb, 2011 1 commit
  3. 10 Feb, 2011 1 commit
  4. 09 Feb, 2011 2 commits
  5. 08 Feb, 2011 2 commits
    • Michael Pyne's avatar
      Allow naming module-sets. · e98912d6
      Michael Pyne authored
      By naming module-sets, it becomes possible (with some more work in this
      commit) to quickly build given module-sets from the command line,
      instead of having to still laboriously give labels to every module
      contained within the set.
    • Michael Pyne's avatar
      Prefer module-specific options to guess scm type. · 1194cc29
      Michael Pyne authored
      kdesrc-build tries to figure out if a module is git-based or svn-based
      automagically. Now the script will see if the 'repository' or
      'svn-server' settings are set directly for a module and if so, those
      factors will take precedence.
      Otherwise kdesrc-build will still prefer an existing .svn directory to
      guess svn, but in the future kdesrc-build will start tending to guess
      git if there's no other info.
  6. 07 Feb, 2011 1 commit
    • Michael Pyne's avatar
      Maintain existing scm type for source directories. · fb5d26a6
      Michael Pyne authored
      With some git module IDs in the XML ending up the same as still-used
      Subversion modules, it makes more sense to maintain the existing status
      of present source directories instead of trying to use the wrong scm
      Later I need to add detection for e.g. "MIGRATED" files to influence scm
      type detection, but this works a bit better for now.
  7. 06 Feb, 2011 10 commits
    • Michael Pyne's avatar
      Use correct value from git-repository-base. · 4f1ca734
      Michael Pyne authored
      I ported to use a key instead of a value.
      In addition, properly tell whether a class method (for package Module)
      is operating as an object method or as a class method.
      I get a lot of errors about things not being a git module, which leads
      me to believe that auto-detecting whether a module is svn or git is no
      longer working, so test with care.
    • Michael Pyne's avatar
      Restore update/build phases in kdesrc-build. · e3756f6d
      Michael Pyne authored
      Basically all I did was hook the new code right in front of the old code
      so it's still a bit messy, but it seems to me that it should work fine
      in theory (all options are still held where they used to be, and the
      update_list and build_list variables are still available and have the
      same type).
    • Michael Pyne's avatar
      Refactor XML searching. · 7696cb03
      Michael Pyne authored
      kdesrc-build now supports building XML modules from the command line
      (well, building is disabled in favor of debugging printouts, but the
      module list gets setup right at least).
      To force a command-line module to be thought of as an XML module,
      precede the name with a +.
      e.g. kdesrc-build --pretend +kde
      is instructive at this point... ;)
    • Michael Pyne's avatar
      Merge branch 'master' into local-xml · d17feacf
      Michael Pyne authored
    • Michael Pyne's avatar
      Update kdesrc-build default modules. · ad523120
      Michael Pyne authored
      This updates the modules that kdesrc-build would build without so much
      as an available config file. This really needs updating to move a
      default configuration file to the build-support git repo and then having
      kdesrc-build simply bootstrap from there. But this will do in the
    • Michael Pyne's avatar
      Get closer to supporting XML modules from CLI. · 0d3fdac6
      Michael Pyne authored
      This change refines module support a bit by introducing a Module object
      for use by the rc-file and command line option-reading code. What's
      needed next is to move the XML module expansion from parse_moduleset to
      occur after process_arguments() and read_options() (but before the
      actual rest of the process, of course).
    • Michael Pyne's avatar
      Merge branch 'xml-support' into local-xml · 2a4c7b6b
      Michael Pyne authored
    • Michael Pyne's avatar
      Merge branch 'master' into xml-support · 8978bc45
      Michael Pyne authored
    • Michael Pyne's avatar
      Stop guessing tag names for kdesupport-for-4.foo · 9e0c2e68
      Michael Pyne authored
      kdesupport used to have tags made up of the form kdesupport-for-4.2,
      kdesupport-for-4.3, etc. which contained the releases of the various
      underlying different libraries that were minimum requirements for the
      corresponding KDE version.
      Now that kdesupport is mostly moved to git, those tags are not being
      created, so don't bother trying to guess them for 4.6 and greater.
    • Michael Pyne's avatar
      Make a new module reading pass. · 56473d0b
      Michael Pyne authored
  8. 05 Feb, 2011 1 commit
  9. 04 Feb, 2011 3 commits
  10. 03 Feb, 2011 1 commit
    • Michael Pyne's avatar
      Fix detection of whether git-stash is needed. · 7c2ee0f7
      Michael Pyne authored
      I broke the code that determines whether git-stash is determined in
      commit 2b0d0d62. The problem is that
      the system() Perl function returns the exit code and miscellaneous
      process exit data (such as whether the process failed to run, etc.)
      and I actually needed that data.
      In the commit I refer to, I switched to my safe_system() which only
      returns the exit code and now kdesrc-build thought there was an error
      running git, when instead git was returning the proper exit code for
      a module with local changes. Thanks to dfaure for the report.
      Not closing the bug here in case I merge this somewhere else later.
  11. 02 Feb, 2011 1 commit
  12. 31 Jan, 2011 4 commits
    • Michael Pyne's avatar
      Add support for projects.kde.org XML database. · 8f663654
      Michael Pyne authored
      This commit adds initial support for the projects.kde.org XML database
      as exported by https://projects.kde.org/kde_projects.xml
      The short story is, to use the "use-xml-modules" option in a
      *module-set*. E.g., what I just tested was with
          use-xml-modules phonon-gstreamer
      end module-set
      If you want --pretend to work you should throw a module set that uses
      XML modules in somewhere and try having the XML-based module built, or
      just download kde_projects.xml yourself and plop it right in the base
      source directory.
      In theory a grouping module (such as extragear/utils) should allow you
      to recursively grab and build every module composed within it.
      However, modules that contain a <repo> tag, and then have children
      underneath also containing <repo> tags only have the very base <repo>
      tag working (if I coded it right ;)
      The reasoning for this is to allow module groups where you can build the
      entire module, or given subsets of it (e.g. Calligra allows this from
      what I can tell, you can build Calligra or assuming you've met the
      dependencies, Krita).
      If a module has no direct <repo> tag, but includes modules or projects
      or whatever that each have their own <repo>, then everything should be
      recursively built.
      kdesrc-build obeys the <active> tag, so modules that claim not to be
      active will not be built by kdesrc-build (at this point, even if
      directly passed on the command line, although that may change later).
      I'm super-tired and won't have time to test throughout much of this
      week, so I've put it in a branch. Feel free to test yourself if you're
      interested though!
      I'd like to thank Allen Winter who contributed the core XML parsing
      code, it was a big boost to getting something working. :)
    • Michael Pyne's avatar
      Show exception messages from git updates. · 27890063
      Michael Pyne authored
      I use exceptions for error conditions the arise from handling git module
      updates, but I never extracted their message in the exception handler.
    • Michael Pyne's avatar
      Update qt-kde repository location. · d6c40372
      Michael Pyne authored
      kde-qt has become qt-kde, and moved from gitorious.org to git.kde.org.
      This updates the locations in the kdesrc-buildrc-sample and the built-in
    • Michael Pyne's avatar
      Do not run git-diff in pretend mode. · 2b0d0d62
      Michael Pyne authored
      I had left git-diff as system() instead of safe_system() (which
      respects --pretend) when looking to see if git-stash needed to be run.
      However, this can sometimes significantly slow down the kdesrc-build -p
      run, and the only real benefit was not confusing users with git diff and
      git diff --cached command lines.
  13. 30 Jan, 2011 1 commit
    • Michael Pyne's avatar
      Merge kdesrc-build doc updates from svn. · d066e357
      Michael Pyne authored
      Awhile ago I started a subversion work branch so that I could
      continue to update the Docbook docs for kdesrc-build. Now that
      kdesrc-build is out of the SC (and the freeze is up anyways) I
      can merge the changes/fixes back in.
  14. 29 Jan, 2011 2 commits
    • Michael Pyne's avatar
      Fix kdepimlibs adjustment in kdesrc-buildrc-sample. · c4e5a8e5
      Michael Pyne authored
      The "use-modules" option is only supported in module-sets as it changes
      the handling of the repository keyword. Other than the the change was
      good. :)
    • Michael Pyne's avatar
      Try to detect svn->git migrations. · 255b2ff0
      Michael Pyne authored
      This just adds some simple logic to see if a Subversion-using module has
      been migrated to git (by looking for a MIGRATION file as per the
      kdepimlibs example).
      Looking for README is possible to code, but many modules already have
      one so I didn't go that route.
  15. 28 Jan, 2011 2 commits
  16. 23 Jan, 2011 4 commits