this post was submitted on 30 Aug 2026
77 points (93.3% liked)

Technology

87685 readers
2699 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
77
I hate packaging my software for Linux (fresh) (getfresh.dev)
submitted 22 hours ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world
45 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] umbrella@lemmy.ml 0 points 8 hours ago* (last edited 5 hours ago) (2 children)

~~that defeats the purpose of a package manager~~

[–] notabot@piefed.social 6 points 7 hours ago (1 children)

Not really. The user adds the repository to the list of repositories their package manager is using, and the packages in that repository appear as normal packages for them to select. When the author publishes a new version of their package it'll appear as an update in all users package managers.

[–] corsicanguppy@lemmy.ca 1 points 6 hours ago

The user adds the repository to the list of repositories their package manager is using,

Fun fact: when we were doing devops as config management, we distributed repository configs AS packages ... which we updated as required.

and the packages in that repository appear as normal packages for them to select. When the author publishes a new version of their package it’ll appear as an update in all users package managers.

So easy.

These days, with CI, ya berge your patch and the fix is built and sent to testing immediately, ready to be assessed for promotion, which then signs and pushes the artifact into the pipeline for synchronization and application everywhere.

Aside from the actual smarts to build a good package, the tooling makes every other part of is zero-friction.

[–] corsicanguppy@lemmy.ca 2 points 6 hours ago (1 children)

that defeats the purpose of a package manager

I suspect you're confusing the package manager with the supply chain. This should always be separate, lest we get some systemd-like spongiform blob with no ability to swap out and improve parts without discarding the whole.

Unless you're Lennart, it's a bad idea.

[–] umbrella@lemmy.ml 2 points 5 hours ago* (last edited 4 hours ago)

yes i was. didn't get great sleep, my bad.