1. 11 Apr, 2021 8 commits
    • Leo's avatar
      main/meson: upgrade to 0.57.2 · 9f3db2f1
      Leo authored
      9f3db2f1
    • Leo's avatar
      main/gdk-pixbuf: upgrade to 2.42.6 · b8255c24
      Leo authored
      b8255c24
    • Leo's avatar
      community/avfs: upgrade to 1.1.4 · f2378838
      Leo authored
      f2378838
    • Leo's avatar
      main/py3-setuptools: downgrade to 54.2.0 · ca7f4b5b
      Leo authored
      unfortunately newer setuptools versions introduces changes that cause
      breakage to a great amount of python3 modules that were written in a
      _PERFECTLY_ acceptable form and some that even followed the _EXAMPLES_
      provided by upstream.
      ca7f4b5b
    • Michał Polański's avatar
      bc89fa02
    • Jakub Jirutka's avatar
      main/npm: disable on mips64* · 76d9df6f
      Jakub Jirutka authored
      76d9df6f
    • Jakub Jirutka's avatar
      main/npm: install global packages into /usr/local/lib/node_modules · 7e17fcb6
      Jakub Jirutka authored
      To avoid mixing npm packages installed by the user using npm with
      packages managed by apk.
      7e17fcb6
    • Jakub Jirutka's avatar
      main/nodejs: move npm into a standalone aport · 25b10bd1
      Jakub Jirutka authored
      npm is bundled in Node.js, but it's a standalone project with its
      own release cycle and version number. main/nodejs provides LTS
      version of Node.js, so it includes old version of npm.
      
      Alpine build tools don't handle subpackages with pkgver different
      from the origin pkgver. Thus the current 'npm' subpackage has version
      14.16.1-r0 (version of the Node.js) which is confusing, because the
      real version of the packaged 'npm' is 6.14.11.
      
      Moreover, npm has gazillion bundled dependencies, so there's a high
      risk of security vulnerabilities; using npm bundled in Node.js
      quite complicates security patching and requires rebuilding complete
      Node.js package.
      
      For these reasons, I think it will be better to split npm into a
      separate aport and provide the latest version instead of some arbitrary
      version bundled in the Node.js tarball.
      
      Actually, I planned this three years ago (see commit message in
      244cc743), but forgot about it.
      
      There's one unpleasant consequence of this change - the latest npm
      version is 7.9.0 which is lower than 14.16.1 (version inherited from
      nodejs package). Since Alpine doesn't have "epoch" version as e.g.
      Fedora, there's nothing I can do about it beside informing the users
      (using nodejs.post-upgrade script).
      25b10bd1
  2. 10 Apr, 2021 23 commits
  3. 09 Apr, 2021 9 commits