[Slackbuilds-users] VBox slackbuild

[Heinz Wiesinger]

On Wednesday, 15 January 2025 21:43:42 CET Jim wrote:
> On Wed, Jan 15, 2025 at 20:18 (+0000), Erich Ritz via SlackBuilds-users 
wrote:
> > On Wednesday, January 15th, 2025 at 1:45 PM, Jim <zsd+slackbuilds at jdvb.ca> 
wrote:
> >> Hi all,
> >> 
> >> Back in November I emailed the Virtualbox Slackbuild maintainer, pointing
> >> out that VBox was up to 7.1, whereas the Slackbuild is at 6.1.50. (And
> >> since then, VBox is up to 7.1.4.)
> >> 
> >> I never heard back. Is anyone in touch with the maintainer (Heinz
> >> Wiesinger)?
> > 
> > This was his comment last time an update request came up
> > (https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-May/02817
> > 6.html):
> > 
> > Is there a specific feature/bugfix you *need* from the newer version
> > though? Generally, the version on SBo should work "just fine".  If it's
> > just about running the "latest and greatest", you should be able to fetch
> > the SlackBuild from my -current or 15.0 repo (or even the packages). I
> > don't typically update my scripts on SBo anymore unless there's a
> > specific reason.
> 
> *My* specific reason was that I updated to a newer kernel (6.10.3), because
> I was having some glitchy issues with one of the components of my laptop.
> And my info at the time was that versions before 7.0.16 would no longer
> compile on 6.10 kernels.
> 
> So I guess you could say "I need a VBox that compiles on 6.10".  (But,
> having said that, I suspect someone is going to tell me that my system
> isn't vanilla, so I'm on my own.)
> 
> korgie at gmail.com: I compiled 7.0.20 and it has been working just fine on
>                   6.10.3 (Slackware64 15.0).
> 
> I agree that maintainers should not feel obligated to spend all day every
> day chasing updates to the packages that they have graciously agreed to
> support.  But, on the flip side, perhaps occasionally, if someone needs a
> newer version for some reason, it is also possible that they might be
> motivated to do an update when requested.
> 
> Anyway, now that you have pointed out Heinz' personal policy, I will know
> to not ask again about this.

Hi Jim,

Sorry, your mail seems to have gotten lost in the noise. The past couple 
months have been unreasonably busy here.

I do have a SlackBuild ready for 7.1.4 for -current in my own repo (not 
advertising that here though. I'm sure you can find that yourself with a bit of 
google-fu ;-) ), but that would need a couple tweaks to get it up on SBo. That 
said, I'm not particularly invested in updating to it for various reasons:

1) 6.x worked better. Nothing major, some minor issue here and there. Just 
enough to make me flinch though.

2) It depends on Qt6, which 15.0 doesn't ship stock and I don't want to depend 
on the SBo version.

Now, 7.0.x could possibly avoid the dependency on Qt6, but it still leaves me 
with my impression of 6.x working better. Barring any major issues I'll thus 
stick to 6.x.

The kernel incompatibility is unfortunate, but like you said, you kinda run in 
non-stock territory there. You're free to pick the -current script and use 
that though :-)

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250115/888701bb/attachment.asc>