NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.

You must log in to comment.

in reply to @NireBryce's post:

u can actually write an ebuild that has its upstream source set to a git repo and if u dont specify a specific git commit it will just check for new commits whenever u run an emerge update. in fact theres a bunch of "latest bleeding commit hope u dont get virus'd" versions of packages in portage that u can enable that do exactly this, for example, mold! https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-devel/mold/mold-9999.ebuild

i wonder now if u could do some funky magic to make it pull like the latest stable tag or smthng

I think the reason there isn’t really anything standalone is: how would the package manager know what commands it should use to compile that software? What about the dependencies?

The only solution I’m seeing is to ask each developers to have a file describing the up-to-date build/installation process and list of dependencies. I guess the closest to that in basically Nix, but it’s not wildly used enough to be really a solution.

I'm not sure 'run shady build scripts on github but don't keep them upgraded' is better than 'run shady build scripts on github, but at least now the vulns are fixed faster'

as for nix, it's also got... I'm not really sure how to explain it, but, the wrong metaphors for what it's trying to do, until you already know them deeply