In my environment I was building two subversion packages with and without the FREEBSD_TEMPLATE option. This allowed me to install the FREEBSD_TEMPLATE version on the system I do FreeBSD work on and the version without on the other systems and avoid confusing my end users with the various FreeBSD specific fields. I did this by creating a local slave port:
# @(#) $Id: Makefile 4 2017-09-10 17:41:11Z leres $ (LBL)
This worked great until yesterday when something changed:
[00:00:03] Error: MOVED: devel/subversion-freebsd 2011-10-16 Merged with devel/subversion
The attached patch adds a freebsd FLAVOR to the subversion port. I'm not sure if using OPTIONS_SLAVE is 100% correct but I couldn't quite figure out how OPTIONS_SLAVE works. Setting OPTIONS_EXCLUDE to FREEBSD_TEMPLATE worked as expected but setting OPTIONS_SET_FORCE did not.
Assuming we can converge on a reasonable version I'm happy to commit this with maintainer approval.
Created attachment 191506 [details]
Created attachment 191507 [details]
poudriere build log (with default options)
Created attachment 191508 [details]
poudriere build log (freebsd flavor)
Created attachment 191676 [details]
freebsd_OPTIONS_SLAVE doesn't actually do anything...
Default build contains FREEBSD_TEMPLATE. Should it be disabled by default?
Created attachment 192686 [details]
Of course you're right; I didn't notice because I have FREEBSD_TEMPLATE disabled... Here's an updated patch.
Mmmmm, I would rather it be reversed, the default "subversion" package stays as it is with FREEBSD_TEMPLATE, and another flavor with another package name is without it.
I'm saying this because many ports depend on subversion, and pkg's dependencies are not clever enough to see that the different flavors both provide subversion with slightly different features.
Given the svn -> git conversion...