Is there a reason for using Travis instead of GitHub’s built-in CI system?
With the GitHub CI system, you can specify your own container image which could have GNU Make 4.4 already pre-installed (you build it once and then re-use it).
RE Travis: I feel quite comfortable and happy w/ Travis already. Additionally, I want to keep my reliance on github minimal. The only reason I’m using it is that it is where things are searched for and found by fellow programmers :-)
RE Container: My home machine is running Tumbleweed which’s had Gnu Make 4.4 for a few months now already. I was trying to make the pipeline behave as closely as possible to the user’s machine who may not have that version installed. Otherwise as you and @sugar_in_your_tea mentioned, I could pack everything I’d need in a container.
You’d just use the container for testing other Make versions. If your users use Ubuntu, run your tests with an Ubuntu docker image. You can run several versions that way with minimal effort.
I don’t know much about Travis, but it’s pretty easy to set that up with Jenkins.
That’s pretty much what I ended up doing. Install Gnu Make 4.4 as part of the pipeline. I then added a check to warn the user if the Make version they use is not supported.
No, I’m saying you’d support older versions of make in your project and use docker images in your CIb pipeline to test each of those supported versions. If you’re not using any 4.4-specific features, 4.2 (20.04) and 4.3 (22.04) would probably work. So you’d have a docker container for every OS that you’re officially supporting (or at least every version of make that supported OSes use).
Guake and only really customized by setting infinite scroll and tweaked transparency. I jump in and out of the terminal all the time, so it’s perfect for me. Plus F12 for terminal is old muscle memory from RISCOS.
DJ Ware adds detailed performance statistics to his reviews.
I don’t think it’s very useful. Easily changeable default choices should make the most notable differences. The filesystem for example. Another big factor should be the configuration and the version of the kernel and it probably changes more between updates than between distributions.
@antihero, there's a few different methods that all attack that problem in perty much the same way. The flatpak in question needs to have access to the theme/font/icon pack you want it to use.
<a class="invalid-href" rel="noopener noreferrer" target="_blank" title="Invalid link protocol">https://docs.flatpak.org/en/latest/desktop-integration.html</a>
It sure what your resolution is, but I’ve been experiencing the first problem as well. MSI support has been great and after a few weeks it’s not happened. They did tell me if it does they will repair it even though it’s outside of warranty. Have you called them?
I’ve called them a few times but it’s been hard since their hours aren’t very long and I have a busy job. But to be honest I wasn’t banking on support since I haven’t ever had good tech support experience. Hearing that you’ve had a good experience, though, I think I’ll get in touch with them, thanks.
Easy actually. I’m on arch (Hyprland) right now, so no longer EOS but it’s been refreshing. I’d recommend EOS as a base for any arch install, better than “arch installer” by a long shot. If you have dedicated storage I’d recommend using it and booting to the respective system through EFI rather than relying on software bootloader (windows likes to break it). I am running arch on a dedicated SSD and it’s been smooth so far.
That would be my plan, I have windows on its own 500gb drive and 2 1tb drives for gaming. My plan would be partition on the gaming drives as they just house the game files.
How much would you recommend allocating to EOS? I’m very much green around the ears when it comes to Linux, I’ve dabbled and have a home server running Manjaro and fumbled my way through that somehow!
If all goes well I’d like to daily drive it and only use Windows for games I can’t get running on EOS
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.