[Slackbuilds-users] sboinstall - jdk download fails

[Eric Pratt]

On Tue, Apr 4, 2017 at 10:26 AM, Matteo Bernardini <
matteo.bernardini at gmail.com> wrote:

> 2017-04-04 19:17 GMT+02:00 Eric Pratt <eric.b.pratt at gmail.com>:
> >  I found this by using HttpFox on Firefox to see what was happening when
> I
> > clicked through the website and downloaded via a browser.  It's
> important to
> > understand that you are still accepting the license agreement by using
> wget
> > to download it.
> >
> > I suspect Slackbuilds is against this practice for a number of reasons,
> > especially the possibly too magical discovery of URLs via text parsing of
> > HTML.  But it's something to consider.  Another idea might be an optional
> > WGET_OPTIONS="" field in the jdk.info file.  That would tell automated
> tools
> > like sbopkg what extra command line options are needed to download from
> the
> > URL given in jdk.info.
>
> the main reason we are against it it's that Oracle request that people
> actually accept the license when downloading the tarball explicitly
> clicking on a radio button (the download page says "You must accept
> the Oracle Binary Code License Agreement for Java SE to download this
> software."): we cannot allow ourself to "cheat" (sorry for the term) a
> silent approval, we have to follow what the vendor asks.
>
> Matteo
>

​I figured this would be the stance which is why I wrote my own script and
don't use the JDK slackbuild.  But I'm sure it's legal because you are in
fact accepting the agreement by sending the header via wget.  The only
issue of legality would be that someone could potentially use sbopkg to
auto-download without explicitly accepting the license agreement.  In that
case, sbopkg would need an ability to accept an option on the command line
or interactive user input to accept the jdk license before performing the
download.

But, if we can't automate this, then I have to admit I don't understand why
the jdk slackbuild even exists on slackbuilds.org.  java.Slackbuild is
provided in the distribution which will create a JDK or JRE package as
desired.  And JDK always includes JRE anyway.  You still have to manually
download the JDK regardless of which one you use.  So what is the benefit
of this slackbuild even existing here?​
​
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170404/111ebaa4/attachment.html>