On 14/5/26 19:05, fsLeg via SlackBuilds-users wrote:
Interesting. And really hacky. I feel like it goes against the principles of
Slackware. Also, if the logic is complex enough, which seems to be the case for
dart-sdk with several moving parts all of which rely on git, you might end up
just reimplementing a rudimentary git. And maintainability is a potential
nightmare. I'm not sure I have the skills to write something that wouldn't rely
on manual hardcoding of the required values.
And what about verifyability? Some random tarball with sources and even blobs
(blame Google) from who knows where with no way of verifying its authenticity
aside for the random maintainer's word. It's not like various mkvendor and
create-tarball scripts work in a reproducible way.
That's why whenever I use a get-*.sh script to generate a tarball to use
in a SlackBuild, I keep the script as one of the files in that
SlackBuild. Then in the README I mention that this "random maintainer"
has used that script to generate the tarball and invite anyone who might
think I'm too random to generate their own tarball using the same
script. Of course they don't have to use that script; they can make
their own arrangements.
chris
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
