ak@ asked that I remove the unused error array, and I went to have a
look at what it was actually used for back in the day. It seemed better
to re-enable the blame feature instead of removing it.
Sponsored by: Absolight
This now warns about these 2 ports as needing to be marked as resurrected:
archivers/brotli|archivers/py-brotli|2016-11-24|Brotli is a python module
devel/libbrotli|archivers/brotli|2017-07-12|meta project no longer required to build libs
www/rubygem-jquery-rails||2017-01-07|Has expired: Depends on deprecated www/rubygem-railties
www/rubygem-jquery-rails4|www/rubygem-jquery-rails|2017-03-27|Remove PKGNAMESUFFIX
bsd.default-versions.mk can rely on ARCH being defined.
- In bsd.port.mk move inclusion of bsd.default-versions.mk from the
pre-makefile section to the options section so the variables can be used
earlier. Also put the bit of code sitting between the options section and
the pre-makefile section into the options section.
- Remove last few cases where ports set WITH_OPENSSL_PORT. This variable is
handled in bsd.default-versions.mk and some ports were setting it after
including bsd.port.options.mk. After FreeBSD 9 EoL all but a few ports,
and then only when setting non-default options, work without setting that
variable.
PR: 215996
Exp-run by: antoine
Approved by: portmgr (antoine)
Summary:
Currently addport -a ends up running a command line like:
make PORTSDIR="/tmp/ap.BsOuZJBy" clean check-categories
where the temporary directory has only parts of the ports tree
(specifically bits under ${PORTSDIR}/Mk) checked out. This can't work
as 'make check-categories' needs to see the entire ports tree checked
out.
Instead, run the checks specified by '-a' and '-t' with the value of
$PORTSDIR from the environment.
Reviewers: crees
Reviewed By: crees
Subscribers: mat
Differential Revision: https://reviews.freebsd.org/D7525
the case $? needs to have the exit status of the grep, not the awk line,
so remove the awk line, it was not really helpful anyway.
Also, with slave ports, most of the time, they don't have
(PORT|DIST)VERSION, try to use CATEGORIES, PKGNAMEPREFIX or
PKGNAMESUFFIX.
PR: 211243
Submitted by: mat
Approved by: maintainer timeout
Sponsored by: Absolight
- allow PORTSDIR to be a symbolic link when looking for expired ports or
dependent ports
- allow for trailing slashes when specifying ports as cat/name. This prevents
the port being a false positive for itself when the Makefile mentions the
port name (e.g., in PLIST_FILES)
- fetch possibly open PRs via Bugzilla, GNATS is long gone. Remove the
version that used freefall. Thanks to crees for pretty-printing the results.
- forcibly delete the temporary checkout to prevent rm(1) from asking for
confirmation on each file in .svn
- add myself as author
Approved by: maintainer (crees)
Differential Revision: https://reviews.freebsd.org/D6396
While there replace USE_SQLITE=x by USES=sqlite:x.
PR: 208971
Submitted by: mat
Exp-run by: antoine
With hat: portmgr
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D5951
If portmgr@ needs to commit against better advise, two years after this was
first discussed without any motion of the upstream.
Drop a few more maintainerships along the way.
The last change was flawed; for deleted ports it was writing out the
origin, but it should be writing out the appropriate ports cache
database directory.
The redundant-opt-file scripts assumes that if options are cached,
then the port that it was created by still exists. This, of course, is
a terrible assumption.
If the cached options refer to a port that has since been deleted or
otherwise no longer exists, just print the origin and continue. The
normal use case is that the origin will be piped to xargs rm -rf which
will purge the obsolete directory as desired.
I got a request to make Synth identify "redundant" cached option files,
where "redundant" means the saved port options are identical to the
default options. For Synth (and portmaster?) which use the port's
cache options, these redundant files are somewhat of a liability. At
best they do nothing (Synth assumes default options) and at worst they
will cause a future build to stop if the maintainer changes the port
options later.
This situation is avoidable. Rather than build detection into Synth,
I decided to write a generic shell script for ports. When run, it
will display the full path to the port's options directory if the
cached options are the same as the defaults. This output is suitable
to pipe to "xargs rm -rf" to remove all the redundant options in a
single command.
1. Check if svnlite is available and use it by default, else: use svn
2. Dehardcode svn binary name in shell calls, to make both svn/svnlite
work
Approved by: crees (maintainer)
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
This is the script that generated the "20 ports account for X% of the
Ports collection by size" report. This shells script is useful to
identify obscenely large ports: top-size-offenders.sh
chkdepschain.py: doesn't support pkgng
explicit_lib_depends.sh: doesn't support pkgng
plist: obsolete; searches for /etc/mtree/BSD.local.dist, add @dirrm, doesn't know about man pages in the plist
release: unused and obsolete
resolveportsfromlibs.sh: doesn't support pkgng
Approved by: portmgr (bapt)
