Date: Mon, 27 Feb 2017 14:54:42 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: How to create a port only for specific FreeBSD releases Message-ID: <7e0c1388-247f-116e-c005-562c77aafd99@FreeBSD.org> In-Reply-To: <AM3PR02MB31216E353C3B32EAA4DA445F6570@AM3PR02MB312.eurprd02.prod.outlook.com> References: <AM3PR02MB31216E353C3B32EAA4DA445F6570@AM3PR02MB312.eurprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --B1anPiNxABqkLeD9K9KQVGJ4rGPVjmk0V Content-Type: multipart/mixed; boundary="KCujoPKTR4pwwXIjo9UHHgOptDmsDSPdm"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Message-ID: <7e0c1388-247f-116e-c005-562c77aafd99@FreeBSD.org> Subject: Re: How to create a port only for specific FreeBSD releases References: <AM3PR02MB31216E353C3B32EAA4DA445F6570@AM3PR02MB312.eurprd02.prod.outlook.com> In-Reply-To: <AM3PR02MB31216E353C3B32EAA4DA445F6570@AM3PR02MB312.eurprd02.prod.outlook.com> --KCujoPKTR4pwwXIjo9UHHgOptDmsDSPdm Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/02/27 14:37, Andrew Hotlab wrote: > Hi to all, I'm trying to make a port which installs only a couple of > simple scripts (thus NO_BUILD, NO_ARCH, and void MASTER_SITES and > DISTFILES...). >=20 > Since these scripts are designed to run on FreeBSD 10.0 and newer, > I'd like to know if there is a way to prevent the port from installing = on > older FreeBSD releases. In the Porter's Handbook I found this paragraph= , > but it seems regarding only ported app's source code: >=20 > https://www.freebsd.org/doc/en/books/porters-handbook/porting-versions.= html Well, given that the earliest supported version in ports is now 10.3-RELEASE, this problem appears to have fixed itself for your purposes= =2E In general, you can test against ${OSVERSION} in your port's Makefile to detect what OS version the port is being built on, and mark the port as broken where the OS version is not suitable. Note however that binary packages are built on the oldest supported version of the major branch, so by marking the port broken for the OSV, you will prevent binary packages being available for that entire major branch. It's best to apply this sort of brokenness determination at the level of the major version number, rather than anything finer grained. Cheers, Matthew --KCujoPKTR4pwwXIjo9UHHgOptDmsDSPdm-- --B1anPiNxABqkLeD9K9KQVGJ4rGPVjmk0V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYtD24XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTn2rMP/0wAnAoG/ca6E/tA5uCfW0wE it/VmkQx/1U47AYFZZGLwKS2jqz10K3zUYiB67USiGnOsh4wE+IxLBHLNwZi5qWx ExAOaX+H5FtZASSzkdF3O+hx6mokyqBxEyipl45uyG2ymCP10d054C5I4qTlUaFH a9FFP7m31sabiIRoSb8oezQZjhNOUc3fcVe6kgLgPB5onPsk1Wtt3tMsbqOtuZFl +0YOEiEg2DGIx5xstLYoN64qeYBjWp2tcV9UK8Qu1GGzDTLrkGnRdxMlVQAhvw4D rl7OQbfrkMsdpqnsFBCmRvLY+DNrgLIy8VpnnJpYQr6hRSfiwyKI+tupvTptSuSj Uu+NAVfiW0hvvOWt/KIdGEh1I/yfurSttwwq7n2XCahim1nw5GA5BUQHQa2al+Ek AonMCocmncpTifXeJwVjsLMFDVWpmNXQwITRRMxaReuVMeSo8AdNBsVjlGuZl5xw 8uf1NTMXlMgQl+tHVlbHq1VL153SVkUXU2+4T+TcX5vULKYf2HVWr+kyf0XLunre fWIz/+05BL/0SvswzfdSfbzRVJ80yOE32lokQsr0xx1BSJsfZzvrrdpnlk3KgabD H4Iq6sTqZ39pzGd3/cW+DiSZg++ttXY1evM5EGJB4gjFo7/R/kadLpHIeUsxbwy2 HB/jAq4JnwwG+5hnQmup =WcPb -----END PGP SIGNATURE----- --B1anPiNxABqkLeD9K9KQVGJ4rGPVjmk0V--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7e0c1388-247f-116e-c005-562c77aafd99>