[Slackbuilds-users] vokoscreen (2.5.0)

Ricardo J. Barberis ricardo at palmtx.com.ar
Mon Apr 13 22:05:39 UTC 2020

El Domingo 12/04/2020 a las 16:18, B Watson escribió:
> On 4/12/20, Rich Shepard <rshepard at appl-ecosys.com> wrote:
> > "And it seems that vokoscreen has been forgotten to transfer to an new
> > owner, after I told the slackbuilds mailing list that I cannot maintain
> > my build scripts anymore.
> This is a common thread... someone abandons their builds, posts to the
> mailing list saying so. People step up and say "I'll take over X, Y,
> and Z" but then they don't follow up by sending in an update with their
> name/email in the .info file. Months or years later, the old maintainer
> is still listed as the current one, and he keeps getting emails for stuff
> he's already publically abandoned. And the new maintainer has possibly
> forgotten he's supposed to be the maintainer...
> I'm as guilty as anyone of this, volunteering to take stuff and then
> forgetting I said it. So there's 2 ways to fix this:
> 1. As soon as you volunteer to take over a build, send in an update
>    with your name/email in the .info file. Do this immediately (or
>    sooner!), because if you wait a couple days, you'll forget.
> 2. The admins monitoring the list can change the .info files and
>    push the changes to git.
> As much as I hate policy and process, I think we should decide on one
> or the other approach and stick to it rigorously.
> Thoughts? This is open to the whole list, not just admins.

I was meaning to ask about this, since I'm also guilty of this :)

If I send an update with only my info changed: should I bump the BUILD version 
or not?

I mean, there's no need to upgrade the package if the only thing that changes 
is the maintainer's name an email but I was never sure and so never sent the 
updates (and some of my newly adopted packages actually need an update but 
life gets in the way).

If the SBo admins want to do it for me, this is my only adopted slackbuild 
that doesn't have my info:

misc/grc (orphaned - no maintainer)

These other 3 I could take over:

libraries/librsync  (Lyle Sigurdson, mailed on 07/01/2020, no answer)
network/urlgrabber  (Javier Rojas, mailed on 07/01/2020, no answer)
system/acpitool     (Rodney Cobb, mailed on 07/01/2020, no answer)

Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

More information about the SlackBuilds-users mailing list