• 1 Post
  • 150 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle






  • As someone that just started modding and playing FNV for the first time about 2 weeks ago in linux, I must say this is one of the best mods for FNV and if you are planning to play the game I would highly recommend all the Viva New Vegas mods including the extended mods. With New Vegas Reloaded installed afterwards. Also I suggest you use a user generated preset for Reloaded. The Reloaded mod fixes a lot of issues I had with Viva New Vegas only and it adds many more features than I thought it would. It also seemed to have made the game run with less crashes too but I would still recommend CASM with MCM to improve the autosave functionality of the base game.

    While I agree that the use of discord is mildy infuriating. I’d like to play some Devil’s avavodo for a moment as someone that uses git almost everyday and teaches trunk based development.

    1. Not everyone knows how to use git. As a modding community they want outside contributions from anyone that is willing to put the time in and make as low as a barrier to entry as possible.

    2. Most of these modders are using windows and even just installing git on windows isnt that easy for the average windows user. Infact i only just recently fugured out how to get mod organizer 2 working properly on linux so I could mod FNV using modorganizer2-linux-installer. For the average windows user, needing to make a git commit to contribute to a modding comunity would be more than mildly infuriating. So I especially see the user generated presets for this never leaving discord unless some kind of pipeline / serverless function was inplace that took the discord file uploads and did a git commit for the user.

    3. Most of these builds are not plaintext and would not benifit from using git versioning. They should also probably make use of use git lfs considering their size which even less people understand how to use lfs compared to normal git.

    I think the easiest solution is to try to copy both the stable and the nightly builds to their github on their own respective branches. And make set them as releases. Idealy this would be automated using guthub actions. This is not a trunk based development approach, but neither is having nightly builds and it would take time to change development philosophy.

    The user generated presets however will take a bit more consideration before moving to github as anyone can upload them and they are made often. But this ultimately should also use github actions and be commited to a different repository possibly in the same organization (or what ever github calls it) as to keep a bit of distance from the official releases.



  • You probably won’t be able to run an LTS kernel on a brand new PC that just hit the market. But using the most recent kernel for arch or a derivative like endevorOS should work after like a week maximum.

    I did have an issue like this on Ubuntu and its what made me actually start distro hopping since it worked fine on fedora and Arch using the latest kernels.




  • CubitOom@infosec.pubtolinuxmemes@lemmy.worldEvery tech thread on Lemmy
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    edit-2
    1 month ago

    I recommend EndeavorOS now to everyone that actually wants to learn linux, or people that don’t want to be “fighting” their os.

    It works enough to not have to do anything to it besides update, including installing nvidia drivers. And it’s arch based so they can just read the arch wiki if they have questions.

    Honestly the only issue ive had with it is one of apps not working on wayland so i just had to switch to x11.

    Its a little less noob friendly than manjaro (they had great guis that make it so you never need to open a terminal at all) but i cant recommend manjaro anymore since they dont support the latest version of pacman.

    As far as an os that’s close to enterprise servers, if they aren’t contanerizing the workloads and running k8s on a distroless (or atleast minimal) base image then i don’t want to work there anyway.


  • In TBD, it’s not a “release” until its production ready. The methodology and philosophy doesn’t prevent you from developing multiple feature branches at once or even deploying a work in progress feature branch to a dev environment.

    All TBD requires in that case is once the feature branch is production ready, it’s merged to the trunk. You may need to add a feature toggle if there are multiple release like for different architectures. And you also might benefit from using git tags and deploying to production from a git tag instead of the most recent commit on a branch.

    Exactly what you need to do is going to depend on the project’s exact needs but TBD is totally possible in that example.