non port: Tools/scripts/check-latest-link |
Number of commits found: 8 |
Monday, 17 Aug 2015
|
14:20 mat
Remove UNIQUENAME and LATEST_LINK.
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
|
Monday, 7 Oct 2013
|
10:54 erwin
no longer point to NO_LATEST_LINK but to PKGNAMESUFFIX instead.
Also mention the latest portmgr blog post.
|
Wednesday, 27 Mar 2013
|
14:03 erwin
Replace linebreak with space instead of comma in address
list, to make the for loop lateron actually work.
|
Friday, 19 Oct 2012
|
14:49 erwin
Sync with the version that's currently running on pointyhat:
- 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
|
Sunday, 8 Apr 2012
|
09:00 erwin
Spell plural LATEST_LINKs with a lowercase s to avoid confusion
to the spelling of LATEST_LINK.
Submitted by: gerald
Feature safe: yes
|
Tuesday, 14 Jul 2009
|
07:58 erwin
Explicitly override LOCALBASE to make sure we don't get
confused by locally installed ports that might influence
PKGNAME or other variables.
Suggested by: pav
|
Friday, 5 Jun 2009
|
16:22 erwin
Force cleaning of the environment from customized local settings.
|
Monday, 24 Jan 2005
|
07:20 kris
Add the script I use to look for duplicate LATEST_LINK entries and to
send nag-mails to the responsible maintainers.
|
Number of commits found: 8 |