[Slackbuilds-users] Source code missing for some Slackbuilds scripts

[Jim]

On Wed, Mar 12, 2025 at 15:22 (-0400), B. Watson wrote:

> On Wed, 12 Mar 2025, Jim wrote:

>> I think you missed or forgot about the discussion of "interrupts
>> vs. polling" in your computer architecture and/or OS classes.  :-)

> People aren't computers though...

Are you sure?  Maybe we're all just part of some big simulation.  :-)


>> I would much rather get interrupted by an email telling me I should/could
>> update a package than spend my time polling one or more web sites to see if
>> there is some issue.

>> YMMV.

> My mileage does vary... I don't want to be interrupted when doing
> something else.

I could argue that you just don't need to read your email when you are
busy.  (But if these emails come frequently, I agree with your point.  At
least to a point.)

> I'll poll for updates when I decide it's time to work on SBo stuff.  When
> I'm busy doing something else, there's no need to know that a build needs
> updating (I'm not gonna work on it because I'm already busy).

> Anyway, any polling process can be turned into an interrupt one by
> running it periodically and emailing the result to your address.  We
> got this handy cron daemon in Slackware...

Sure, if you have an way to automatically check each of your Slackbuilds
for updates.  I know you have a lot, and for you that makes sense.  But for
people who have a small number (back to the varying mileage), setting that
up may not make sense, depending on whether or not the source repository
makes automatically checking for updates easy.

                                        Jim