[Slackbuilds-users] hope this isn't a stupid question

[Alexander Grotewohl]

Simple answer is yes. Treat the VM as if it were another machine.

That said it's possible to do the slackbuild dev/testing on slackware-current, but it takes quite a bit more effort (and library duplication, which you'd be doing in the VM anyways)

I'm sure someone else can offer more information on the second option if it appeals to you.

--
Alexander Grotewohl
https://dcclost.com

________________________________
From: SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> on behalf of Glenn Becker <glenn.becker at gmail.com>
Sent: Wednesday, April 8, 2020 9:43:27 AM
To: SlackBuilds.org Users List <SlackBuilds-users at slackbuilds.org>
Subject: [Slackbuilds-users] hope this isn't a stupid question

Hi -

I am thinking of buying a smallish laptop to dedicate to Slackware. I've usually done double-, triple- and occasionally more- boot machines, but my distro-hopping is (I think!) coming to an end.

And I was wondering ... if I ran slack-current as my main system, but ran slack-stable in a VM, could I use the latter to work on my SlackBuilds? I'm by no means well-versed in what is possible or impossible with VMs.

Thanks,

Glenn Becker

------------------------------------------------------------------------------------------------------------------------
"Doctor, I have come to ask you to tell me everything you know about the night."
                                                      - Djuna Barnes, Nightwood
------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200408/490d643d/attachment.htm>