1. 24 Jun, 2014 2 commits
  2. 23 Jun, 2014 1 commit
  3. 12 Jun, 2014 1 commit
  4. 10 Jun, 2014 2 commits
  5. 02 Jun, 2014 1 commit
  6. 25 May, 2014 3 commits
  7. 23 May, 2014 4 commits
  8. 22 May, 2014 2 commits
  9. 07 May, 2014 1 commit
  10. 04 May, 2014 3 commits
  11. 21 Apr, 2014 2 commits
  12. 27 Mar, 2014 7 commits
  13. 16 Mar, 2014 1 commit
  14. 13 Mar, 2014 1 commit
  15. 12 Mar, 2014 4 commits
    • Allan McRae's avatar
      makepkg: enforce fakeroot usage · d8ee8d0c
      Allan McRae authored
      
      
      Packaging outside of fakeroot can result in incorrect permissions for
      package files.  It has been years since fakeroot issues during packaging
      were common, so it is safe to enforce fakeroot usage.  If using fakeroot
      is impossible for some reason, a two line wrapper script will suffice to
      fool makepkg.
      
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      d8ee8d0c
    • Allan McRae's avatar
      makepkg: Remove --asroot option · 61ba5c96
      Allan McRae authored
      
      
      The days of fakeroot being error ridden are long gone, so there is no
      valid reason to run makepkg as root.
      
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      61ba5c96
    • Pierre Neidhardt's avatar
      makepkg: Add a --noarchive option to inhibit archive creation · ce3fbcb1
      Pierre Neidhardt authored and Allan McRae's avatar Allan McRae committed
      
      
      1. Packagers who want to test the package() function, i.e. to check the content
      of the pkg/ folder.
      
      2. Developers who want to check how the packaged version of a program looks, in
      other words how the pkg/ folder looks.
      
      3. For users of systems with no port tree, makepkg can ease package creation.
      However the resulting archive of the whole makepkg process is often useless.
      
      For all situations, makepkg will usually be called several times. But no archive
      (the final package) is needed in any cases. The archive creation ends up being a
      waste of time and resource, especially for big applications and slow machines.
      
      Since this option aborts the process prematurely, it behaves like the
      -o,--nobuild option, i.e. any other option acting on later stages in the process
      will be automatically discarded. For --noarchive, it means that in
      
        $ makepkg --noarchive --install
      
      the '--install' option does not do anything.
      
      Signed-off-by: default avatarPierre Neidhardt <ambrevar@gmail.com>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      ce3fbcb1
    • Pierre Neidhardt's avatar
      makepkg: Comment on install_package() return code · 20415868
      Pierre Neidhardt authored and Allan McRae's avatar Allan McRae committed
      
      
      Previously, install_package() return code was either used as exit code or
      ignored. This was rather confusing. The return code is now always ignored and a
      comment on install_package() has been added.
      
      Signed-off-by: default avatarPierre Neidhardt <ambrevar@gmail.com>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      20415868
  16. 08 Mar, 2014 2 commits
  17. 04 Mar, 2014 3 commits