pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2019-11-04	sysutils: align variable assignments	rillig	1	-2/+2
	pkglint -Wall -F --only aligned --only indent -r Manually excluded consolekit and dc-tools since pkglint didn't get the formatting correct.
2019-09-02	Changed PYTHON_VERSIONS_INCOMPATIBLE to PYTHON_VERSIONS_ACCEPTED; needed for ↵	adam	1	-2/+2
	future Python 3.8
2019-04-26	Omit mentions of python 34 and 35, after those were removed.	maya	1	-2/+2
	- Includes some whitespace changes, to be handled in a separate commit.
2018-07-03	extend PYTHON_VERSIONS_ for Python 3.7	adam	1	-2/+2

2017-09-04	Update some URLs.	wiz	1	-2/+2

2017-01-01	Add python-3.6 to incompatible versions.	wiz	1	-2/+2

2016-07-09	Remove python33: adapt all packages that refer to it.	wiz	1	-2/+2

2015-12-05	Extend PYTHON_VERSIONS_INCOMPATIBLE to 35	adam	1	-2/+2

2015-11-04	Add SHA512 digests for distfiles for sysutils category	agc	1	-1/+2
	Problems found with existing digests: Package memconf distfile memconf-2.16/memconf.gz b6f4b736cac388dddc5070670351cf7262aba048 [recorded] 95748686a5ad8144232f4d4abc9bf052721a196f [calculated] Problems found locating distfiles: Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9 Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2014-12-16	Fix build with py-setuptools-0.8.	wiz	1	-2/+2

2014-06-03	security/py-{cybox,stix,libtaxii} and sysutils/py-pefile do not seem to have	khorben	1	-1/+3
	been ported to either Python 3.3 or 3.4.
2014-05-17	Import py27-pefile-1.2.10-139 as sysutils/py-pefile (from wip)	khorben	4	-0/+58
	pefile is a multi-platform Python module to read and work with Portable Executable (aka PE) files. Most of the information in the PE Header is accessible, as well as all the sections, section's information and data. pefile requires some basic understanding of the layout of a PE file. Armed with it it's possible to explore nearly every single feature of the file. Some of the tasks that pefile makes possible are: * Modifying and writing back to the PE image * Header Inspection * Sections analysis * Retrieving data * Warnings for suspicious and malformed values * Packer detection with PEiD's signatures * PEiD signature generation