Skip to content
Snippets Groups Projects
  1. May 10, 2015
  2. May 01, 2015
  3. Mar 29, 2015
  4. Mar 16, 2015
  5. Mar 15, 2015
  6. Feb 14, 2015
    • John Crispin's avatar
      scripts: fix getver git dir check · 59acb0b8
      John Crispin authored
      
      Git internals are referenced by .git which isn't necessarily a
      directory. It may also be a file that references the actual .git
      directory using the gitdir directive.
      
      If .git is assumed to be a directory the build will not be able to get
      the correct version when openwrt is included as a git submodule because
      when used as a submodule .git will actually be a file referencing to a
      subdirectory in the parent's git dir.
      
      When the correct version is not detected some image generation tools
      will fail because the OpenWrt string will be 'OpenWrtunknown' which is
      too long for some header formats.
      
      Signed-off-by: default avatarFelix Kaechele <heffer@fedoraproject.org>
      
      SVN-Revision: 44452
      59acb0b8
  7. Feb 10, 2015
  8. Feb 09, 2015
    • John Crispin's avatar
      build: propagate override information to .config file · e2684c21
      John Crispin authored
      
      With this change, override information is now parsed from the metadata
      and put in the %packages hash. A new hash - %overrides - is created and
      exported, to be used during the .config-package.in generation.
      
      If an override is detected, a new option CONFIG_OVERRIDE_PKGS will be
      created in the .config, and will contain a space-separated list of all
      the overridden packages.
      
      Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>
      
      SVN-Revision: 44336
      e2684c21
    • John Crispin's avatar
      build: allow openwrt.git packages to be replaced by feeds · 2e2c0477
      John Crispin authored
      
      Currently, replacing a package available in openwrt.git requires
      modifications in openwrt.git, or requires duplicating the package in a
      feed but with a different name, which causes all kind of problems
      related to dependencies (all packages selecting it would have to be
      modified accordingly to select the new package).
      
      With this change, if a package with the same name is present both in
      feeds/ and package/ folders, the one in feeds/ can override the one
      in package/, both in the menuconfig and during the build, by passing the
      "-f" option to "./scripts/feeds install"
      
      This mechanism is particularly useful for vendor tree, or in general for
      application which needs to replace one particular package which exists
      within openwrt.git by a custom/newer version.
      
      Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>
      
      SVN-Revision: 44334
      2e2c0477
  9. Jan 29, 2015
  10. Jan 23, 2015
  11. Jan 22, 2015
    • John Crispin's avatar
      build: revert r44076 · b6f268d7
      John Crispin authored
      
      the patch causes issues when installing feeds
      
      Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>
      
      SVN-Revision: 44078
      b6f268d7
    • John Crispin's avatar
      build: allow openwrt.git packages to be replaced by feeds · de3bf7e4
      John Crispin authored
      
      Currently, replacing a package available in openwrt.git requires
      modifications in openwrt.git, or requires duplicating the package in a
      feed but with a different name, which causes all kind of problems
      related to dependencies (all packages selecting it would have to be
      modified accordingly to select the new package).
      
      With this change, if a package with the same name is present both in
      feeds/ and package/ folders, the one in feeds/ can override the one
      in package/, both in the menuconfig and during the build, by passing the
      "-f" option to "./scripts/feeds install"
      
      This mechanism is particularly useful for vendor tree, or in general for
      application which needs to replace one particular package which exists
      within openwrt.git by a custom/newer version.
      
      Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>
      
      SVN-Revision: 44076
      de3bf7e4
  12. Jan 08, 2015
  13. Dec 13, 2014
  14. Dec 12, 2014
  15. Dec 10, 2014
  16. Dec 07, 2014
  17. Nov 28, 2014
  18. Nov 24, 2014
  19. Nov 14, 2014
  20. Oct 26, 2014
  21. Oct 14, 2014
    • John Crispin's avatar
      scripts: fix wrong usage of '==' operator · 20940138
      John Crispin authored
      
      [base-files] shell-scripting: fix wrong usage of '==' operator
      
      normally the '==' is used for invoking a regex parser and is a bashism.
      all of the fixes just want to compare a string. the used busybox-ash
      will silently "ignore" this mistake, but make it portable/clean at least.
      
      this patch does not change the behavior/logic of the scripts.
      
      Signed-off-by: default avatarBastian Bittorf <bittorf@bluebottle.com>
      
      SVN-Revision: 42911
      20940138
  22. Oct 13, 2014
    • John Crispin's avatar
      scripts/feeds: handle missing/broken feeds better · 590b855c
      John Crispin authored
      pts/feeds update -a" can fail rather silently for feeds using git, as
      the script does not pause when updating a feed fails. Instead it prints the
      error message and calmly continues to the next feed. It is very easy to
      overlook update errors with the feeds updated first, as their text scrolls
      rapidly away from the screen.
      
      This behaviour has not been a big problem with svn feeds, as svn update stops
      with a conflict message and interactively forces the user to resolve or
      postpone the conflict. In any case the svn error is noticed by the user.
      
      Majority of the feeds use now git, so this silent failure can affect users
      doing private builds in an increasing amount.
      
      Below is an example of update failing and script continuing:
      
      perus@v1404:/Openwrt/barrier$ ./scripts/feeds update -a
      Updating feed 'packages' from
      'https://github.com/openwrt/packages.git;for-14.07' ...
      remote: Counting objects: 17, done.
      remote: Compressing objects: 100% (15/15), done.
      remote: Total 17 (delta 10), reused 8 (delta 1)
      Unpacking objects: 100% (17/17), done.
       From https://github.com/openwrt/packages
      62031da..dc26009  for-14.07  -> origin/for-14.07
      Updating 62031da..dc26009
      error: Your local changes to the following files would be overwritten by merge:
      utils/collectd/Makefile
      Please, commit your changes or stash them before you can merge.
      Aborting
      failed.
      Updating feed 'luci' from 'http://git.openwrt.org/project/luci.git;luci-0.12' ...
      Already up-to-date.
      Create index file './feeds/luci.index'
      Updating feed 'routing' from
      'https://github.com/openwrt-routing/packages.git;for-14.07' ...
      ...
      
      The script prints "failed.", but does not break the updating process. The
      "update_feed" function returns an error code 1, but that value is not checked
      in the "update" function, which continues to the next feed.
      Return 1 as error:
      ​https://dev.openwrt.org/browser/trunk/scripts/feeds#L547
      Call to update_feed without any error monitoring:
      ​https://dev.openwrt.org/browser/trunk/scripts/feeds#L585
      
      
      
      The included patch makes the feeds script to stop updating after failing to
      update a feed.
      
      The script continues to the refresh_config step despite a possible failure in
      updating, so the stopping action just prevents the other feeds from updating
      and makes the error more clearly visible.
      
      Signed-off-by: default avatarHannu Nyman <hannu.nyman@iki.fi>
      
      SVN-Revision: 42891
      590b855c
Loading