ports/Tools/scripts/README, branch 13.1-eol

strip_RECORD.py: move to Mk/Scripts

2023-03-09T11:18:17Z

Requested by: mat

Tools/scripts: add strip_RECORD.py

2023-03-09T03:20:24Z

Strips/prints only the first column of a Python wheel's RECORD file. To be used as part of the USE_PYTHON=autoplist process.

Mk: remove ancient 'make update-patches' target.

2022-09-28T07:48:20Z

People should use 'make makepatch' instead which creates patches with the expected filename and header. Differential Revision: https://reviews.freebsd.org/D36767

Tools/scripts: remove addport

2022-05-09T19:06:06Z

The addport script is no longer useful since git has been introduced in April 2021, just use plain "git add" instead. Do not forget to add the port name to the category Makefile and mention the contributor in the contributors article in the doc repository. Differential Revision: https://reviews.freebsd.org/D35104

Tools/scripts: Add port_conflicts_check.lua

2022-01-22T11:48:03Z

Add a script to check the CONFLICTS and CONFLICTS_INSTALL parameters of ports for completeness and correctness. This script uses the "hidden" LUA interpreter in the FreeBSD base system and the pkg-provides extension of the pkg command to check for conflicting files in all packages available for the architecture and version of the base system this command is run on. It generates output in the following format: portedit merge -ie 'CONFLICTS_INSTALL=kicad-library-footprints-devel \ # share/kicad/template/fp-lib-table' \ /usr/ports/cad/kicad-library-footprints (The last line is shown wrapped for the text of this commit message.) The portedit command is provided by the port-fmt package. It takes care of placing the CONFLICTS_ENTRY into the correct position of the port's Makefile (and removes prior definitions). The files listed with each result are examples of files that are in conflict between the port and the packages in the list after ">". The main purpose of the files list is to help distinguish between conflicts that affect all flavors or versions of a port, or whether the files are placed in version specific sub-directories or use other mechanisms to allow e.g. multiple Python versions to co-exist. (In the latter case ${PYTHON_PKGNAMEPREFIX} can be used to limit the CONFLICTS_INSTALL entry to conflicting packages using the same Python interpreter version, for example, else a prefix like py*- might be required for a version independent pattern). Users of this feature are highly advised to check each Makefile by comparing it with pre-edit version before the changes are committed! There are several limitations that can cause incorrect or undesirable changes: - The list of files installed by each port is only available for the officially built packages (and the flavors selected from the set of available flavors). It does not include ports that may not be packaged or that are broken or ignored due to a dependency on a broken port (or for other reasons). As a result, there may be undected conflicts with ports for which no official package is available. - The CONFLICTS_INSTALL line is not always inserted into the correct position in the Makefile, typically due to out-of-order entries used by portedit to locate the desired position. - Complex ports may have conditional CONFLICTS_INSTALL entries, depending on port options or flavors that are in effect. It is not possible to deal with that kind of Makefiles in an automated way. - The union of all CONFLICTS and CONFLICTS_INSTALL entries is used as the list of install conflicts of a port. But only CONFLICTS_INSTALL entries are generated by this tool. Quite a lot of ports have CONFLICTS entries where CONFLICTS_INSTALL would suffice (i.e. there is no build conflict, actually), but there are ports that need to keep the conflicts listed as CONFLICTS. Such issues can be found by comparing the before and after versions of the edited Makefiles. - Conflicting ports that have been removed from the ports system will only be found as long as their official package files are still available. (There is a recommendation that conflicts with removed ports are kept for a few months.) - If all packages conflicting with a given port have been removed from the ports system and the official packages repository, the now superfluous CONFLICTS_INSTALL definition will not be detected. This is due to only Makefiles of ports being parsed that install files in the same place as some other port. Parsing all Makefiles instead would increase the run-time of this script by more than a factor of 10.

Tools/scripts: Add new script update_crates to replace CARGO_CRATES block

2021-11-14T22:45:25Z

Simple shell script to help updating Makefile CARGO_CRATES variable returned by make cargo-crates. simplest way to use it : make cargo-crates | update_crates Makefile > NewMakefile

cleanup: remove LEGAL and (support in) related tools.

2021-06-11T13:45:10Z

LEGAL is badly maintained, LEGALlint notices quite a number of ports which mismatch their line in LEGAL. The port itself is always leading. * math/giacxcas: restrict RESTRICTED_FILES to giac_* only Differential Revision: https://reviews.freebsd.org/D30061 Reviewed by: portmgr (mat), dch, eadler, marcus

framework: Remove $FreeBSD$

2021-04-06T14:27:10Z

Where appropriate fiddle with a few other things.

Remove two tools that are no longer useful with Git.

2021-04-06T10:39:46Z

- mfh: this is replaced by 'git cherry-pick -x HASH' - psvn: unlike svn, git has no per-file properties Adjust README accordingly. Differential Revision: https://reviews.freebsd.org/D29451 With hat: portmgr

Stop documenting scripts which no longer lives in the tree

2019-09-05T14:18:46Z

PR: 226606 Submitted by: Sergey Akhmatov