User Details
- User Since
- May 9 2014, 10:23 AM (629 w, 3 d)
- Roles
- Administrator
Wed, May 27
Sat, May 23
Wed, May 20
Wed, May 6
Apr 28 2026
Apr 26 2026
Apr 22 2026
I don't think removing entries without checking how long they have been unused is a good idea,
Apr 19 2026
Apr 17 2026
Apr 8 2026
Apr 1 2026
Mar 29 2026
Mar 25 2026
Mar 24 2026
Mar 15 2026
Mar 9 2026
Mar 7 2026
Mar 4 2026
Well, like everything committer related, it's in the committer's guide https://docs.freebsd.org/en/articles/committers-guide/#ports-exp-run, but I don't see what would break with this change.
I don't think this should break too many things.
Mar 2 2026
Mar 1 2026
Feb 28 2026
Feb 22 2026
Feb 21 2026
Feb 18 2026
Feb 16 2026
Feb 8 2026
Jan 24 2026
This looks good to me.
Jan 21 2026
Jan 18 2026
Jan 10 2026
Jan 7 2026
Jan 3 2026
Dec 30 2025
This looks good, could my comments be addressed ?
Dec 22 2025
Dec 18 2025
Dec 17 2025
Dec 8 2025
It feels ok to me, yes.
Maybe there is a need to add some autotools env variables too, or maybe those should go in Templates/config.site.
Dec 6 2025
Nov 27 2025
Nov 25 2025
Using must is a no.
This rule should not be absolute.
You can advise people to not put a variable, but variables may need to happen from time to time.
The WWW variable is there so make(1) can create things out of it.
The ports tree is to be used by developpers, not end users. End users have packages and should not have to interact with the ports tree ever.
If a developper needs to know the actual value, they can run make -V WWW, we could even add a few targets, like make open-www that would do stuff like xdg-open "${WWW}".
