[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2014Q2 2009-08-02T17:56:44Z 2009-08-02T17:56:44Z joerg joerg@pkgsrc.org 2009-08-02T17:56:44Z urn:sha1:7dd297e86e75ff567691e5bf00e01275d5e011c7 Make pkg_install WARNS=4 clean and fix a number of lint warnings. Based on reports from veego about warnings with older GCC releases in pkg_delete, where a variable is potentially used uninitialized. 2009-02-02T12:34:59Z joerg joerg@pkgsrc.org 2009-02-02T12:34:59Z urn:sha1:d7cc6db11bfefd0006364a122a40572d9eb9b739 - DB support is always included from libnbcompat if needed - pkg_view and linkfarm are not installed any more; they are not moved into the attic yet, so they can easily be installed as separte package - common configuration file to customise the behavior of various components; this supersedes the old audit-packages.conf - support for PKSC7 signatures (using X509 certs) and GPG signatures for packages in a secure way. See pkg_admin(8) for how to create them and pkg_install.conf(5) for the options to use them - audit-packages and download-vulnerability-list are wrapper scripts around pkg_admin. They try to mimic the classic options if used sanely. "pkg_admin audit" is now an order of magnitude faster than before - pkg_add uses libarchive and libfetch instead of external ftp and tar: - progress bar is currently missing for downloads - "pkg_add -" is no longer supported - no adhoc check for conficts between dependencies and already installed packages - "pkg_add -s" has been replaced with an option in pkg_install.conf, verification of plain detached GPG signatures is no longer supported - optional check for vulnerabilities before adding a package - if /var and /usr/pkg are on different fileystems it is twice as fast now - conflicts due to overlapping plists are checked before installation - pkg_add no longer plays with the process limits - pkg_add and pkg_delete have a new destdir option; scripts have to either be modified to use PKG_DESTDIR or should be disabled - pkg_add -u for now can't be used to update to the exact same version - internal "rm -rf" and "mkdir_p" code - all memory allocation failures are not explicitly fatal - if a file is not removed due to a failed checksum, still remove the entry from pkgdb 2008-04-29T05:46:08Z martin martin@pkgsrc.org 2008-04-29T05:46:08Z urn:sha1:d86d72404ea77b61bf693d3b43c72ab7ebf42956 2007-09-18T15:44:18Z joerg joerg@pkgsrc.org 2007-09-18T15:44:18Z urn:sha1:79ba801833ef7fd86023a8614f550dd3dac09907 and free it. 2005-12-06T01:08:09Z ben ben@pkgsrc.org 2005-12-06T01:08:09Z urn:sha1:d0a9fc6a674f0d2f268fbbc58b5145e0dcf98bb9 Modify pfcexec so the new process file name can be different from argv[0]. This fix is from Peter Postma, and it addresses PR#32228 2005-11-23T04:49:51Z ben ben@pkgsrc.org 2005-11-23T04:49:51Z urn:sha1:f1c76720818742646aa6086511d57c2002b876bf and add PAX_CMD fallback macro. 2005-11-22T15:44:59Z ben ben@pkgsrc.org 2005-11-22T15:44:59Z urn:sha1:df7be8ce2f4f055c4ab1e8c23c843f83176cd9ac problems. Instead, use exec*() functions. Replace PUSHOUT() macro and string buffers with a function that operates on data structures. If it is necessary to copy files into place from staging area, then use pax to copy them. Add functions in pexec.c to create a pipe for sending data to a child process. Replace pipe code in create/perform.c with these functions. Use these functions instead of command-line arguments when copying files into place from staging area. Three system() references remain: @exec, @unexec, and vsystem(). 2003-10-29T23:00:27Z jlam jlam@pkgsrc.org 2003-10-29T23:00:27Z urn:sha1:3607b06f5c4be50fce1a26c0fbcffffa68e38c15 New features include fetching binary packages using HTTP (thanks wiz!) and some minor speed optimizations for pkg_delete. 2003-09-23T13:22:37Z grant grant@pkgsrc.org 2003-09-23T13:22:37Z urn:sha1:dbe2b165b6372a5248bdcc802fc13b950addfa73 2003-09-23T07:13:45Z grant grant@pkgsrc.org 2003-09-23T07:13:45Z urn:sha1:7e46cd752c8ebe61ead37573fa23cbca4dcf0e71