[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2014Q2 2010-04-20T21:22:38Z 2010-04-20T21:22:38Z joerg joerg@pkgsrc.org 2010-04-20T21:22:38Z urn:sha1:84bee4addfb911dfac32dc72adb0e4a6ee18dc32 Fix an off-by-one in the check for properly sized pkgdb entries. It rejected perfectly valid entries. 2010-04-14T18:24:58Z joerg joerg@pkgsrc.org 2010-04-14T18:24:58Z urn:sha1:0447709a57d8dc1616b2ff998ad27c64ead6906b - Try to detect common forms of pkgdb corruption and issue a warning in that case. - Refactor the pkg_vulnerabilities logic to use the compression support from libarchive. This reduces the amount zlib/bzip2 interaction to the linkage. 2010-01-22T13:30:41Z joerg joerg@pkgsrc.org 2010-01-22T13:30:41Z urn:sha1:4c4efbcf34dc06619376ce18f39fbb416b985673 - Refactor man pages: - Move description of environmental variables into pkg_install.conf(5) - Remove a bunch of dead references - Avoid using hard-coded path names that can easily be overridden by the user. - Refactor pkgdb related logic, so that -K behaves consistently. - Add some helper functions to isolate more places from the pkgdb layout. - Sync license list. - Handle PKG_REFCOUNT_DBDIR consistently as option too. - Utilize connection cache from libfetch. - Add helper target for cat pages updates. 2009-10-22T22:51:29Z joerg joerg@pkgsrc.org 2009-10-22T22:51:29Z urn:sha1:b3bcc7f40b7227bdd32ec4d5444ffe9aa5dc3615 Do not overwrite a string with itself using snprintf. This breaks setting the pkgdb directory internally on Linux. Explicitly check if the string is the same and otherwise just use xstrdup. 2009-09-11T18:00:12Z joerg joerg@pkgsrc.org 2009-09-11T18:00:12Z urn:sha1:705d617c2bd5471421c2c918ce5db3844dd4fa61 - Cleanup configure.ac to not check for headers and functions not used - Always use nbcompat/db.h on !NetBSD (PR 41865) - Don't bother setting termwidth in pkg_info, it is never used. 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-03T13:49:56Z joerg joerg@pkgsrc.org 2009-02-03T13:49:56Z urn:sha1:97f4088f5d42e039d93ce38198b8c20454f2071c 2009-02-03T13:18:03Z joerg joerg@pkgsrc.org 2009-02-03T13:18:03Z urn:sha1:2b915dcf8f053a992cef0776de1881020719a86c For PR 40544. 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