aboutsummaryrefslogtreecommitdiff
path: root/Tools
Commit message (Collapse)AuthorAgeFilesLines
* Tools/scripts/update-rust-port.sh: Fix failures that occurred for some portsYuri Victorovich2023-12-191-9/+8
|
* Tools/scripts: Improve update-rust-port.shYuri Victorovich2023-07-121-2/+20
| | | | | | | | * use strict shell mode * check dependencies * update PORTREVISION Suggested by: mikael@ (use of portedit)
* Tools/scripts: Add update-rust-port.sh script to simplify Rust port updatesYuri Victorovich2023-07-121-0/+69
| | | | | | | The command 'update-rust-port.sh <version>', when run in the Rust port directory, updates this port to the requested version. update-rust-port.sh should work in most cases.
* Tools/scripts/rmport: do not add a trailing colon when only removing one portRene Ladan2023-06-031-1/+3
| | | | Reported by: sunpoet (via private mail)
* Tools/scripts: rmport: force cleaning up at the endRene Ladan2023-05-201-0/+2
|
* Tools/scripts/bump_revision.pl: default on -l instead of -gBaptiste Daroussin2023-05-111-4/+4
| | | | | | -g option means also bump portevision of indirect dependencies, this is not required by default since at least FreeBSD 11 when we stopped recursively copying DT_NEEDED
* Tools/scripts/rmport: also cleanup when being trapped on a signalRene Ladan2023-04-301-4/+2
| | | | This should get rid of stale gitrmlist* and gitlog* files.
* Tools/scripts/rmport: remove extraneous trailing '/' in single-port commit ↵Rene Ladan2023-04-301-1/+1
| | | | messages
* Tools/scripts/rmport: try to fix flow for amending the final commitRene Ladan2023-04-301-1/+1
|
* Tools/scripts/rmport: update copyright yearRene Ladan2023-04-301-1/+1
|
* strip_RECORD.py: move to Mk/ScriptsCharlie Li2023-03-092-47/+0
| | | | Requested by: mat
* Tools/scripts: add strip_RECORD.pyCharlie Li2023-03-092-0/+47
| | | | | Strips/prints only the first column of a Python wheel's RECORD file. To be used as part of the USE_PYTHON=autoplist process.
* Tools/scripts/bump_revision.pl: updateMatthias Andree2023-03-041-67/+77
|
* Tools/scripts/rmport: Fix my EnglishRene Ladan2023-02-191-1/+1
| | | | Reported by: George L. Yermulnik <yz@yz.kiev.ua>
* Tools/scripts: use a port-specific commit message if removing a single port.Rene Ladan2023-02-191-1/+10
| | | | | | | This helps in `git shortlog`, replacing "cleanup: Remove expired ports" by "category/port: Remove expired port" for a given category and port. Reported by: gerald
* Tools/scripts/add-port-to-category-makefile.sh: Add export LC_ALL=CYuri Victorovich2023-01-311-0/+2
| | | | | PR: 268737 Suggested by: bdrewery@
* Tools/scripts: Add add-port-to-category-makefile.sh, command that adds new ↵Yuri Victorovich2023-01-161-0/+48
| | | | | | port to category's Makefile PR: 268737
* Tools/scripts: note that you should also be in sync with origin/mainRene Ladan2022-12-041-1/+1
|
* Mk: remove ancient 'make update-patches' target.Rene Ladan2022-09-282-119/+0
| | | | | | | People should use 'make makepatch' instead which creates patches with the expected filename and header. Differential Revision: https://reviews.freebsd.org/D36767
* cleanup: remove support for FreeBSD 13.0 which expired today.Rene Ladan2022-09-011-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Mk/bsd.port.mk: mark 13.0 as unsupported - Tools/scripts/portsearch: Drop support for FreeBSD <= 4 - archivers/zstd: revert "Fix build on FreeBSD 13.0" - deskutils/xdg-desktop-portal: remove check for 13.0 - devel/libpeas: remove outdated comment - editors/imhex: remove compatibility for 13.0 - editors/libreoffice: remove compatibility for 13.0 - editors/openoffice-4: remove compatibility for 13.0 - editors/openoffice-devel: remove compatibility for 13.0 - emulators/linux_base-c7: remove compatiblity for 13.0 - graphics/drm-kmod: remove detection for 13.0 - graphics/gpu-firmware-amd-kmod: do not check 13.0 anymore - graphics/linux-c7-libdrm: remove support for 13.0 - math/igraph: remove support for 13.0 - net/asterisk16: drop support for ancient FreeBSD versions - net/asterisk18: drop support for ancient FreeBSD versions - security/openssl*: drop now obsolete patches - sysutils/bhyve+: drop support for FreeBSD 13.0 - sysutils/ebsnvme-id: drop support for FreeBSD 13.0 - sysutils/openzfs: remove detection of FreeBSD 13.0 - sysutils/openzfs-kmod: drop detection of FreeBSD 13.0 - www/firefox: generalize pkg-message a bit regarding hgame(4) - x11/xorg-cf-files: remove support for FreeBSD < 6 (yes, pre-2008) While here, regenerate patches for: - x11/xorg-cf-files - net/asterisk16 - net/asterisk18 While here, remove a stale $Id$ from Tools/scripts/portsearch Differential Revision: https://reviews.freebsd.org/D36233 Reviewed by: office (fluffy), x11 (manu), arrowd, brnrd, cperciva, freqlabs, imp, jbeich, madpilot, nobutaka
* MOVEDlint: ignore make.confBaptiste Daroussin2022-08-241-2/+2
| | | | | | Ignoring make.conf when looking up for existing flavors, makes the test less likely to be polluted by end user defaults, like default version of python etc.
* Scripts: remove now inaccurate gnomedepends.pyBaptiste Daroussin2022-08-231-126/+0
|
* MOVEDlint: Test the first and second field for spacesBaptiste Daroussin2022-08-231-0/+12
| | | | | both fields should not have spaces in their field, let's make MOVEDlint check for it
* MOVEDlint: exit 1 in case of errorBaptiste Daroussin2022-08-231-0/+2
|
* MOVEDlint: accept -v blame=1 from command lineBaptiste Daroussin2022-08-231-5/+7
|
* MOVEDlint: check for flavored version of a portBaptiste Daroussin2022-08-231-1/+5
| | | | | | There is no need to document when a port has been flavored or new flavor has been added, check if someone added such a line, and prevent the person it is not needed
* MOVEDlint.awk: add the ability to select a start dateBaptiste Daroussin2022-08-231-1/+14
| | | | | Reviewed by: tcberner Differential Revision: https://reviews.freebsd.org/D36304
* Tools/scripts: update port_conflicts_check.luaStefan Eßer2022-05-221-0/+15
| | | | Check that the package file database exists and that it is up-to-date.
* Tools/scripts: update port_conflicts_check.luaStefan Eßer2022-05-201-48/+194
| | | | | | | | | | | | | This update provides the following enhancements: - The list of all files of all packages in the official repository is directly parsed from a dump of the provides.db database, instead of parsing the output of "pkg provides". - If a package uses a version specific sub-directory as is the case for e.g. most perl or python modules, a pattern that is generated that matches only other modules built for the same interpreter version.
* Tools/scripts: remove addportRene Ladan2022-05-092-627/+0
| | | | | | | | | 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: limit scope the script searchesMatthias Fechner2022-03-281-1/+1
| | | | | | The script now searches on limited depth and ignores distfiles folder. Reported by: diizzy
* Tools/scripts: Add port_conflicts_check.luaStefan Eßer2022-01-222-0/+349
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/bump_revision.pl: Minimal updateMatthias Andree2022-01-171-12/+24
| | | | | to deal with ports that have flavors renaming the main port, for instance e2fsprogs-nobootfsck.
* tindex: add new compression format for INDEXBaptiste Daroussin2021-11-221-2/+7
| | | | | | | | | | Add zstd (faster to decompress) and xz (smaller) compression for INDEX Results are the following: 39552 INDEX-14 2366 INDEX-14.bz2 1625 INDEX-14.xz 1672 INDEX-14.zst
* Tools/scripts: Add new script update_crates to replace CARGO_CRATES blockRodrigo Osorio2021-11-142-0/+65
| | | | | | | | 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: drop support for EOL FreeBSD 11.XRene Ladan2021-09-301-6/+2
| | | | | | | | | | | | | | | | | Search criteria used: - 11.4 - OSREL* - OSVER* - *_FreeBSD_11 Input from: - adridg: devel/qca-legacy - jbeich: _WITH_DPRINTF, _WITH_GETLINE, GNU bfd workarounds - sunpoet: security/p5-*OpenSSL* Reviewed by: doceng, kde, multimedia, perl, python, ruby, rust Differential Revision: https://reviews.freebsd.org/D32008 Test Plan: make index
* rmport: first check if we are in a git checkout, then check for changes.Rene Ladan2021-09-081-4/+4
|
* rmport: use "cleanup" instead of "*/*"Rene Ladan2021-07-031-1/+1
|
* cleanup: remove LEGAL and (support in) related tools.Rene Ladan2021-06-113-49/+1
| | | | | | | | | | | 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
* Tools/scripts/rmport: satisfy path check hookRene Ladan2021-05-311-1/+1
|
* Tools/scripts/getpatch: Add SPDX identifierSofian Brabez2021-05-281-0/+3
|
* Tools/scripts/rmport: differentiate exit codes.Rene Ladan2021-04-211-5/+5
|
* tindex: Amend last commit a bit.Mathieu Arnold2021-04-081-4/+2
| | | | | | | | | | | | | | | | | | | | | | | When you run `git log foo` foo can be, from git-log(1), `[<revision range>] [[--] <path>...]`, so, may things. - A "revision range" described by gitrevision(7) (don't got there unless you have a few hours, or already lost your sanity), which can be : * a commit hash, * a tag * a branch, * a ref name * a "describe output" * and many other ways to describe revisions * a range made by any of the above - An existing path. When it can't find any of those, git figures out that you meant something else and made a typo, and exits. If you really meant a path, you have to run `git log -- foo`. Then git knows that you meant a path and only a path, it will then assume that you knew what you meant, and will go look in the history.
* tindex: fix when INDEX fails and ports are deleted since the last success.Rene Ladan2021-04-081-2/+4
| | | | | | | | | | | `git log' cannot get the log of a non-existent file, which the script uses to obtain the last person who touched a port, so check if the file exists before getting its log. This is similar to the Subversion case, which only inspected changed files. The Git version still also checks added ports. While here, call git in blame() using the predefined global variable. Reported by: antoine
* Cleanup executable bits, prompted by 9e1d7c39a1fa.Mathieu Arnold2021-04-081-0/+0
|
* rmport: ready for gitRene Ladan2021-04-061-4/+19
| | | | | | | | | - do not remove ports immediately but store them in a temporary file and remove them once the script has iterated over all ports to be removed. This prevents failed searches. The Subversion version used a temporary worktree so the main tree was unaffected. - remove a "merge" from a question, we use rebase now. - check if INDEX is readable and exit if not
* rmport: fix and simplify workflowRene Ladan2021-04-061-9/+3
| | | | | | | | | | | | - gather information about the deleted port for the commit message before removing the port. I somehow missed that when testing the script. - Instead of a temporary branch, just operate on the current branch and incorporate upstream changes with git pull --rebase. This prevents one from being stranded on a temporary branch if the script crashes and oblivates the need for a squash merge [1] Suggested by: mat [1]
* all: Remove all other $FreeBSD keywords.Mathieu Arnold2021-04-062-4/+0
|
* framework: Remove $FreeBSD$Mathieu Arnold2021-04-0626-46/+2
| | | | Where appropriate fiddle with a few other things.
* Tools/scripts/rmport: convert workflow to git.Rene Ladan2021-04-061-160/+86
| | | | | | | | | Do not push the final result automatically yet, unlike its previous Subversion version. Reviewed by: emaste, mat, uqs Approved by: crees (maintainer, implicit) Differential Revision: https://reviews.freebsd.org/D29451
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 01:49:59 +0000