| index : pacman | |
| Archlinux32 fork of pacman | gitolite user |
| summaryrefslogtreecommitdiff |
| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-02-10 | build-aux/update-copyright 2019 2020 | Allan McRae | |
| Signed-off-by: Allan McRae <allan@archlinux.org> | |||
| 2019-10-23 | Update copyright years | Allan McRae | |
| make update-copyright OLD=2018 NEW=2019 Signed-off-by: Allan McRae <allan@archlinux.org> | |||
| 2018-10-21 | message.sh: add modifications from output_format.sh | Eli Schwartz | |
| In the spirit of making libmakepkg more useful as a library, and, critically, *using* that library for additional pacman scripts, we should include all of output_format.sh and term_colors.sh directly in libmakepkg and hopefully stop having to embed additional copies in e.g. repo-add via m4 macros. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org> | |||
| 2018-10-21 | makepkg: send messages to stdout rather than stderr | Eli Schwartz | |
| This behavior is confusing, since it means absolutely everything goes to stderr and makepkg itself is a quiet program that produces no expected output??? The only situation where messages should go to stderr rather than stdout, is with --geninteg which is meant to return the checksums on stdout (but we don't want to totally get rid of status messages when redirecting the results elsewhere, or, worse, redirect status messages to a PKGBUILD). For this specific case, redirect message output to stderr in the --geninteg callers directly. Implements FS#17173 Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org> | |||
| 2018-03-14 | Update coyrights for 2018 | Allan McRae | |
| make update-copyright OLD=2017 NEW=201 Signed-off-by: Allan McRae <allan@archlinux.org> | |||
| 2017-01-04 | Update copyright years | Allan McRae | |
| Signed-off-by: Allan McRae <allan@archlinux.org> | |||
| 2016-10-22 | libmakepkg: generate all scripts | Alad Wenter | |
| In order for the scripts to be used in testsuites, it is easiest to generate all of them so they are found in the build directory (which may be different to the source directory). Signed-off-by: Alad Wenter <alad@archlinux.info> Signed-off-by: Allan McRae <allan@archlinux.org> | |||