aboutsummaryrefslogtreecommitdiffstats
path: root/Tools/scripts/check-latest-link
Commit message (Collapse)AuthorAgeFilesLines
* Remove UNIQUENAME and LATEST_LINK.mat2015-08-171-80/+0
| | | | | | | | | | | | | | | | | 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
* no longer point to NO_LATEST_LINK but to PKGNAMESUFFIX instead.erwin2013-10-071-4/+3
| | | | Also mention the latest portmgr blog post.
* Replace linebreak with space instead of comma in addresserwin2013-03-271-1/+1
| | | | list, to make the for loop lateron actually work.
* Sync with the version that's currently running on pointyhat:erwin2012-10-191-2/+5
| | | | | | | | | - be less verbose to be more friendly to running from cron - I've been running this script for several years now, not Kris - Send me a copy of the output for debugging Feature safe: yes
* Spell plural LATEST_LINKs with a lowercase s to avoid confusionerwin2012-04-081-1/+1
| | | | | | | to the spelling of LATEST_LINK. Submitted by: gerald Feature safe: yes
* Explicitly override LOCALBASE to make sure we don't geterwin2009-07-141-0/+1
| | | | | | | confused by locally installed ports that might influence PKGNAME or other variables. Suggested by: pav
* Force cleaning of the environment from customized local settings.erwin2009-06-061-0/+5
|
* Add the script I use to look for duplicate LATEST_LINK entries and tokris2005-01-241-0/+72
send nag-mails to the responsible maintainers.