Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't doubt it, but I actually really hate that the build system is a bunch of bash scripts, github actions and assuming the previous stage builds fine. Especially when the custom image forkable repo has an action commented out to squeeze more temporary storage out of GHA hosted runners because some images don't even fit on those (like the gnome-deck). I wish the entire setup was a little more decoupled and maybe allowed you to build multiple stages in one go so the entire system was more "forkable" and less spread out. I went on a bit of a wild goose chase trying to build Bazzite without the Firefox RPM removed (rpm-ostree doesn't like adding and removing and then adding packages again).

I did voice that concern in some Bazzite-related spaces before and it felt like it got brushed off with a weird undertone.



Fork and remove this line: https://github.com/ublue-os/bazzite/blob/main/Containerfile#...

Note that we remove rpm Firefox for security reasons. You do not want your browser to only update with your entire operating system.


Press "y" before linking to a Github file/line to ensure it stays accurate https://github.com/ublue-os/bazzite/blob/5e8f61a56ca3da02778...


I had no idea there was a hotkey for that. Thank you!


Even better, doing so allows GitHub to insert a source snippet if you paste a link like that into an issue or comment.


Yeah, I just always used the context windows to set permalink. Saves me a step now!


My pleasure!


This is cool, but also broken. If you click "raw" after pressing y without reloading, the link is still to a tag/branch.


What do you mean by "to ensure it stays accurate"? Why wouldn't it be accurate if you're just copy-pasting the link?


is the link to the file as it exists on "main" currently, or at a specific revision, so in three years, it will still refer to that version of the file?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: