1. 27 Mar, 2011 6 commits
  2. 26 Mar, 2011 1 commit
  3. 21 Mar, 2011 2 commits
  4. 19 Mar, 2011 2 commits
    • Dan McGee's avatar
      Move the extravars work to the PKGBUILD parser · 641ab66b
      Dan McGee authored and Rémy Oudompheng's avatar Rémy Oudompheng committed
      
      
      Add an additional fake package variable '%SETVARS%' that shows the
      currently defined variables when processing a PKGBUILD. Use this list in
      the extravars rule instead of broke-ass regex parsing that will never
      catch every possible corner case.
      
      Also update the tests accordingly. Variables defined inside a function
      are nothing we are going to worry about at the moment, so safely ignore
      them. Add a legal variable to ensure we don't have any false positives,
      and fix our own misgivings in the PKGBUILD parser so we aren't polluting
      the namespace.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      Signed-off-by: Rémy Oudompheng's avatarRémy Oudompheng <remy@archlinux.org>
      641ab66b
    • Dan McGee's avatar
      Revert "Reduce the amount of false positives in extravars rule." · 59edc2c3
      Dan McGee authored and Rémy Oudompheng's avatar Rémy Oudompheng committed
      This reverts the non-test portions of commit
      e2044d45
      
      .
      
      This is not the proper way to fix this, and we most definitely should
      not have to parse, subprocess, or do anything with bash more than once,
      especially in a rule. We also shouldn't assume everyone has a perfectly
      clean environment with no extra variables exported and defined. Revert
      the entire thing, minus the added test, with a better fix on the way.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      Signed-off-by: Rémy Oudompheng's avatarRémy Oudompheng <remy@archlinux.org>
      59edc2c3
  5. 14 Mar, 2011 3 commits
  6. 13 Mar, 2011 5 commits
  7. 04 Mar, 2011 3 commits
  8. 27 Feb, 2011 13 commits
  9. 26 Feb, 2011 5 commits