▲ 86 ▼ I hate packaging my software for Linux (fresh) (getfresh.dev) submitted 1 month ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world 52 comments fedilink hide all child comments
[–] umbrella@lemmy.ml -1 points 1 month ago* (last edited 1 month ago) (4 children) that defeats the purpose of a package manager permalink fedilink source parent hideshow 4 child comments replies: [–] notabot@piefed.social 6 points 1 month ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] corsicanguppy@lemmy.ca 1 point 1 month 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. permalink fedilink source parent [–] corsicanguppy@lemmy.ca 2 points 1 month ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] umbrella@lemmy.ml 1 point 1 month ago* (last edited 1 month ago) yes i was. didn't get great sleep, my bad. permalink fedilink source parent
[–] notabot@piefed.social 6 points 1 month ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] corsicanguppy@lemmy.ca 1 point 1 month 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. permalink fedilink source parent
[–] corsicanguppy@lemmy.ca 1 point 1 month 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. permalink fedilink source parent
[–] corsicanguppy@lemmy.ca 2 points 1 month ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] umbrella@lemmy.ml 1 point 1 month ago* (last edited 1 month ago) yes i was. didn't get great sleep, my bad. permalink fedilink source parent
[–] umbrella@lemmy.ml 1 point 1 month ago* (last edited 1 month ago) yes i was. didn't get great sleep, my bad. permalink fedilink source parent