[Slackbuilds-users] VBox slackbuild

[Jim]

A two-in-one reply, in hope of keeping this thread from exponentially
expanding...

On Wed, Jan 15, 2025 at 22:38 (+0100), Matteo Bernardini wrote:

> Il giorno mer 15 gen 2025 alle ore 22:07 Jim <zsd+slackbuilds at jdvb.ca> ha
> scritto:

>> 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,

<snip!>

> Hi Jim,

> I noticed Heinz provides a build script for current (that I haven't tested
> myself) on his personal repository

> https://repo.liwjatan.org/pprkut/current/source/virtualbox/

> I don't know if it works on stable but it's worth a try...

Hi Matteo,

Thanks for pointing that out.  What I didn't explicitly say before (when I
mentioned I had already compiled 7.0.20) was that I had indeed used a
SlackBuild to compile 7.0.20.

The one I downloaded was from https://github.com/mdinslage/Custom_SlackBuilds




On Wed, Jan 15, 2025 at 22:38 (+0100), Heinz Wiesinger wrote:

> 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)?

<snip>

Hi Heinz,

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

No problem.  It didn't take me too long to get something up and running.

> 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.

Huh.  I haven't noticed any unimprovements (fortunately).  Having said
that, these days I only use VirtualBox occasionally.

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

I was about to say "That is a very very good reason.".  However, for my 7.0.20
        ldd /usr/lib64/virtualbox/VirtualBox | grep Qt
only shows libQt5 libraries.

> 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.

OK, that's fine.

> 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 :-)

Thanks very much, I appreciate you getting back with all this information.

At this point 7.0.20 works for me, and I am not feeling the need to update
just for the latest and greatest.

Cheers.
                                Jim