[Slackbuilds-users] ripe-atlas-tools

[fourtysixandtwo]

Hey Jeremy,

Sorry for the confusion, the "fixes" I was referring to in that email
were the ones already discussed, but not yet applied to all the
templates (the intended but overlooked part).  Specifically the minor
find and PKGDOC changes.

Adding the rust templates was long overdue and we needed a starting
point.  Good/better ideas are always welcome for discussion, the
templates are not set in stone.  Start a new email thread about them
when you are ready.

Cheers.
fourtysixandtwo

On Fri, 16 Oct 2026 at 00:55, Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
>
> On Wed, Oct 14, 2026 at 2:31 PM fourtysixandtwo <fourtysixandtwo at sliderr.net> wrote:
>>
>> nnb mentioned most of what I was going to say already except there's a
>> few more fixes coming to the templates that we overlooked previously.
>
>
> Were there discussions about potential template changes that I missed (besides the find command that was brought to this list by B. Watson)? I had ideas I wanted to share, and I imagine others have ideas that might be worth considering before pushing big changes. However, I assumed there wouldn't be massive template changes before the attempt to get the repo ready for 16.0, which is why I kept them to myself for now.
>
> It seemed reasonable that these discussions would've happened on the mailing list before making changes to the stable templates, which is why I didn't create a thread about my handling of crate files and the resulting SlackBuild (my script also needed some refinement, which I hadn't felt rushed to do since I assumed big template changes would've only occurred once SBo went into development mode for the 16.0 release). My implementation might not be the best, but maybe the one in the templates isn't the best either and pushing it out to the community might've resulted in an even better implementation. However, adding the version to the templates that was added without discussion shoehorns us into that implementation when better options might exist.
>
> The fact there are additional changes needed to these templates for fixes that were overlooked further solidifies that big changes like these should be sent out to the masses for review before implementation. The issues might've been caught before there were official template updates. I didn't reply to the email about the changes to the templates (even though I was really frustated when I saw it) simply because it seemed like it had already been decided by the admins, but knowing there are addtional "fixes" that need to be made, it reinvigorated my desire to vent my frustration that the majority of these changes were made without community involvement.
>
> None of this criticism is directed specifically towards fourtysixandtwo, it was simply the email I replied to after finding out there were going to be additional changes to fix the changes to the templates.
>
> Jeremy, aka bassmadrigal
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


-- 
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/