Date: Sat, 29 Jun 2024 19:48:55 +0200 (CEST) From: Chris Moerz <freebsd@ny-central.org> To: FreeBSD Virtualization Mailing List <freebsd-virtualization@freebsd.org> Subject: Re: OS Images(Linux/etc) in ports tree Message-ID: <d4156558-9a22-092e-c984-883710fa0ae9@ny-central.org> In-Reply-To: <CA%2B1FSii3a_%2BH43-8VkxDT%2BpW_tM9b93cW8zYx6bLTmWGmz8heQ@mail.gmail.com> References: <CAD6yh%2BM_Z_HNcPavt4_TvGn9QhWPX8Q2qU12em3bUkfNXS1WSA@mail.gmail.com> <28dd6abb-5868-e42a-c385-37e72653ba2d@ny-central.org> <bur66nu6ytk7n5nnriwjy2oddrczsk3wse3zjvv2g6giaiohbl@xpbsmba6kp47> <CA%2B1FSii3a_%2BH43-8VkxDT%2BpW_tM9b93cW8zYx6bLTmWGmz8heQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Sat, 29 Jun 2024, Mario Marietto wrote: > I think that it may be possible to put only the VM config files on the ports,not necessarily heavy image files. > You're all making a valid point; I second that - I read the original post as if we're talking about scripts that download images from somewhere else. May have jumped to conclusions. We can probably all agree: OS images do not belong into the ports tree. Porting scripts that handle OS image creation or downloading them from some public repository though would certainly be fine. chrishome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d4156558-9a22-092e-c984-883710fa0ae9>