Query: All Stories

	Include stories about projects I am a member of.

Cleaned up builddeps and rundeps, fixed make_install for correct libdir

Cleaned up builddeps and rundeps

Disable creation of static library

Hi, I'm afraid I need someone to hand-hold me here.

In D6946#111179, @JoshStrobl wrote:

Not sure why @kyrios123 didn't ever land his patch :P Waiting for him to either do the honors or I'll land either one. Don't really care.

Sadly this thing expects a few different keys than what %CONFOPTS% uses, and using it breaks the configuring. :/

Update to 1.8.2. Bug fixes and other minor improvements.

I very much believe that the demand for CONFIG_HYPERV in Solus will be rising in the future

More python 2.7 stuff went away and not a tear was shed.

Not sure why @kyrios123 didn't ever land his patch :P Waiting for him to either do the honors or I'll land either one. Don't really care.

There's like 5 items in the changelog. Otherwise LGTM.

Not to be "that guy" but there is like...3 items in the changelog. Surely we could just add those.

Update qgis to 3.8.2

pkgconfig builddeps should also be alphabetized, runc removed as a rundep since it'll be a dep of conman.

LGTM. I'll concede on the description, I'm just used to most projects shipping appdata which we would utilize instead of eopkg index data.

Yea this is much much cleaner. I'd rather have a couple other sources that may be overkill than a billion pkgfiles.

Yea let's go ahead and add it as a rundep and remove it as a rundep from podman since conmon is a rundep of it.

Update ipscan to 3.6.0

Update vorta to 0.6.22

Update whois to 5.5.1

Update certbot to 0.37.2

Update compton to 7.3

Update python-acme to 0.37.2

Initial inclusion of D-Feet

Initial repository construction

Update opera-stable to 63.0.3368.43

Add maintainers file

Can you ad yourself as maintainer?

Well.. lets agree to disagree :) Honestly, I understand your doubts, but I very much believe that the demand for CONFIG_HYPERV in Solus will be rising in the future.

Sure but none of that has to do with enabling Hyper-V support in our kernel modules. My point was, you are asking us to support a niche-of-a-niche use-case and I'm not sure that we want to support yet another hypervisor.

The reason I brought up WSL was more of showing the path Microsoft is taking with Linux. If you want pure examples of modern Windows applications/services that are relying on the hypervisor there is Device Guard and Credential Guard. The latter is the reason for that I can not turn off or remove Hyper-V on my work laptop.

That's patently false. WSL is more a replacement for Cygwin than anything. It's not a VM and doesn't afford the same kind of isolation. It also doesn't rely on Hyper-V as much as you think. It's much closer to WINE than an actual hypervisor solution.

I agree that VirtualBox itself is not going anywhere, but VirtualBox (and VMware Workstation) on Windows hosts are in fact leaving the building - at least from Microsofts point of view which eventually often becomes the Windows users point of view. There is the Windows Subsystem for Linux (WSL) steadily growing, a linux kernel in Windows 10 itself and support for nearly all other distributions now as pure virtual machines in Hyper-V. It is still possible (at this date) to get rid of Hyper-V on Windows 10, but it gets harder and harder for each release since the hypervisor in Hyper-V is more and more used in other Microsoft applications and developer tools (like WSL) as well.

I can't say I see the need for it. VirtualBox is not going anywhere, contrary to what you might think. And in order to use Hyper-V you have to have at least a Windows Pro or Enterprise license. The majority of Windows installs on Laptops and Desktops are going to be Windows Home Edition, which doesn't even support Hyper-V. So I would think it exceptionally rare for even a Linux reviewer to have a more advanced license. We also support VMWare Workstation through open-vm-tools which is far more common than Hyper-V amongst reviewers.

My main usecase is that VirtualBox is slowly but steadily fading away in the Windows ecosystem, as VirtualBox and Hyper-V can not coexist. More and more applications i Windows depend on parts of Hyper-V, not just Hyper-V itself. So for people that would be interested to review or try out Solus in a Windows 10 environment (or as in my personal case, use my work laptop to work with diffrerent virtual machines) it is just not possible, while many other distributions offer this possibility. Right now I am using Ubuntu MATE running Hyper-V and xRDP with very good results.

Applied changes for Josh

Add MAINTAINERS.md file

All Stories
Use Results
Edit Query
Hide Query

Yesterday

All StoriesUse ResultsEdit QueryHide Query

Yesterday

All Stories
Use Results
Edit Query
Hide Query