[Slackbuilds-users] REQUIRES="%README%"

[J]

I agree with the concept that the README is required reading always.  
if the user skips that step, the user should expect a SlackBuild to  
fail, or count him or her self lucky if it works. For this reason  
%README% in REQUIRES does not seem to make much sense.

it also does not serve a purpose as a way to stop automation tools  
since the choice of what to do with it is not that of the REQUIRES  
contents or the SBo's author or anything other than the automation  
tool in question.

incidentally sbotools used to do something with this information...  
prompt the user or just stop or such if %README% was encountered,  
regardless of the presence or absence of other entries in REQUIRES.  
but at some point this was unintentionally changed and the test cases  
are unfortunately not complete so the change was not caught... and so  
we just drop the %README% bit on the floor and forget about it. I'm  
not going to fix it because I think this is the right thing to do  
anyway, as indicated above; read the README or expect failure.

I vote for removal.

J


Quoting Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Arrrgh. All these years and I still forget to actually add the
>> attachment.
>
> i have removed %README% on my packages (digikam and wxGTK3)
> Thanks for spotting it :)
>
>
> - --
> Willy Sudiarto Raharjo
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlMVtrAACgkQiHuDdNczM4EqlACgknrLsmLGGSq7tf11T77AxAMf
> qwcAn1eqP6OF1/tDaE6ZYz6F49X5WiYO
> =BChq
> -----END PGP SIGNATURE-----
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/