[Slackbuilds-users] [Slackbuilds-user] Teamviewer3 EULA bypass

King Beowulf kingbeowulf at gmail.com
Wed Oct 28 01:10:58 UTC 2020

On 10/24/20 1:13 AM, Matteo Bernardini wrote:
> As for me I agree with your points and with your proposed solution.
> Il sab 24 ott 2020, 01:30 Dave Woodfall <dave at slackbuilds.org
> <mailto:dave at slackbuilds.org>> ha scritto:
>     I must admit that I'm a bit uncomfortable with this, and I wouldn't
>     want anything to backfire on SBo for hosting it.  In my mind it's no
>     worse than having to download jdk etc. source manually to build it.
>     Just because it's an inconvenience for build tools is no reason to
>     try to bypass what the developers are trying their hardest to have
>     people read, and there may be good reason for someone to *want* to
>     read it to understand if they agree and want to continue to install
>     it, or not, as the case may be.
>     I would put a note in the README about it and leave it at that.
>     What do the other admins think?

[SOLVED] The admin(s) have spoken.

As it is written, so shall it be done.

Note in README advising not to walk away so that the user may read the
fine EULA (RTFE).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x5EFC0C696EB574B7.asc
Type: application/pgp-keys
Size: 9218 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20201027/c68ea18a/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20201027/c68ea18a/attachment-0001.asc>

More information about the SlackBuilds-users mailing list