[mirror_zfs-debian.git] / debian / zfs-dkms.templates

Template: zfs-dkms/stop-build-for-32bit-kernel
Type: boolean
Default: true
_Description: Abort building ZFS on a 32-bit kernel?
 You are attempting to build ZFS against a 32-bit running kernel.
 .
 Although possible, building in a 32-bit environment is unsupported and
 likely to cause instability leading to possible data corruption. You
 are strongly advised to use a 64-bit kernel; if you do decide to
 proceed with using ZFS on this kernel then keep in mind that it is at
 your own risk.

Template: zfs-dkms/stop-build-for-unknown-kernel
Type: boolean
Default: true
_Description: Abort building ZFS on an unknown kernel?
 You are attempting to build ZFS against a running kernel that could not
 be identified as 32-bit or 64-bit. If you are not completely sure that
 the running kernel is a 64-bit one, you should probably stop the build.
 .
 Although possible, building in a 32-bit environment is unsupported and
 likely to cause instability leading to possible data corruption. You
 are strongly advised to use a 64-bit kernel; if you do decide to
 proceed with using ZFS on this kernel then keep in mind that it is at
 your own risk.

Template: zfs-dkms/note-incompatible-licenses
Type: note
_Description: Licenses of ZFS and Linux are incompatible
 ZFS is licensed under the Common Development and Distribution License (CDDL),
 and the Linux kernel is licensed under the GNU General Public License Version 2
 (GPL-2). While both are free open source licenses they are restrictive
 licenses. The combination of them causes problems because it prevents using
 pieces of code exclusively available under one license with pieces of code
 exclusively available under the other in the same binary. 
 .
 You are going to build ZFS using DKMS in such a way that they are not going to
 be built into one monolithic binary. Please be aware that distributing both of
 the binaries in the same media (disk images, virtual appliances, etc) may
 lead to infringing.
Commit	Line	Data
da1f1cc8 CALP	1	Template: zfs-dkms/stop-build-for-32bit-kernel
	2	Type: boolean
	3	Default: true
1ecf651f AX	4	_Description: Abort building ZFS on a 32-bit kernel?
1ecf651f AX	5	You are attempting to build ZFS against a 32-bit running kernel.
da1f1cc8	6	.
1ecf651f AX	7	Although possible, building in a 32-bit environment is unsupported and
	8	likely to cause instability leading to possible data corruption. You
	9	are strongly advised to use a 64-bit kernel; if you do decide to
	10	proceed with using ZFS on this kernel then keep in mind that it is at
	11	your own risk.
da1f1cc8 CALP	12
	13	Template: zfs-dkms/stop-build-for-unknown-kernel
	14	Type: boolean
	15	Default: true
1ecf651f AX	16	_Description: Abort building ZFS on an unknown kernel?
	17	You are attempting to build ZFS against a running kernel that could not
	18	be identified as 32-bit or 64-bit. If you are not completely sure that
	19	the running kernel is a 64-bit one, you should probably stop the build.
da1f1cc8	20	.
1ecf651f AX	21	Although possible, building in a 32-bit environment is unsupported and
	22	likely to cause instability leading to possible data corruption. You
	23	are strongly advised to use a 64-bit kernel; if you do decide to
	24	proceed with using ZFS on this kernel then keep in mind that it is at
	25	your own risk.
4c8f5221 AX	26
	27	Template: zfs-dkms/note-incompatible-licenses
	28	Type: note
	29	_Description: Licenses of ZFS and Linux are incompatible
	30	ZFS is licensed under the Common Development and Distribution License (CDDL),
	31	and the Linux kernel is licensed under the GNU General Public License Version 2
	32	(GPL-2). While both are free open source licenses they are restrictive
	33	licenses. The combination of them causes problems because it prevents using
	34	pieces of code exclusively available under one license with pieces of code
	35	exclusively available under the other in the same binary.
	36	.
c85aa4ce AR	37	You are going to build ZFS using DKMS in such a way that they are not going to
	38	be built into one monolithic binary. Please be aware that distributing both of
	39	the binaries in the same media (disk images, virtual appliances, etc) may
	40	lead to infringing.