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. On May 14, 2026 10:00:27 GMT+03:00, Shahab Vahedi <[email protected]> wrote: >May 14, 2026 fsLeg via SlackBuilds-users: > >> What about cases where the build process relies on the source tree being a >> proper git repo as it uses commit history? > >What if you have a `git` script that mocks the desired output and you put it >in the PATH so it will take precedence over `/usr/bin/git`? _______________________________________________ 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/
