# Package manager A software tool that installs, removes, and upgrades software packages and handles their dependencies. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Inside Appwrite's new build cache: 4x faster dependency installs DevFeed: [Inside Appwrite's new build cache: 4x faster dependency installs]() Original publisher: [Read original article]() Author: Torsten Dittmann Published: 2026-08-13T00:00:00Z Content type: article Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Caching](), [Cache](), [Deployment](), [Next.js](), [Package manager](), [Compression](), [cloud-infrastructure]() Tags: [cache](), [compression](), [dependencies](), [deployment](), [engineering](), [filesystem](), [next-js](), [object-storage](), [pnpm](), [production]() ### AI overview Appwrite's build network caches dependencies between builds for sites and functions. The cache is restored before installation and saved after successful builds, with snapshots isolated per resource. The article explains how Appwrite uses SquashFS images to efficiently store and unpack package-manager data, reporting faster installs for example Next.js applications. ### Source excerpt A deep dive into how Appwrite now caches your dependencies between builds, and what it means for your deployment times. ## Introducing bun, a new package manager and JavaScript runtime environment DevFeed: [Introducing bun, a new package manager and JavaScript runtime environment]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-06T01:58:25Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [Bun](), [Package manager](), [JavaScript](), [Playwright](), [Node.js]() Tags: [bun](), [bun-create-playwright](), [getting-started](), [installation](), [javascript](), [node-js](), [playwright](), [test-automation](), [typescript]() ### AI overview This article examines Bun as a JavaScript package manager and runtime, including its use with Playwright projects. It explains how Bun compares with npm, Yarn, and pnpm, and discusses its integrated tooling and claimed performance advantages. ### Source excerpt New job? New toolset to explore! In this post I'll be investigating a new JavaScript package manager and runtime environment called bun.sh. You may have noticed on Playwright.Dev's Getting Started / Installation section there are three different ways to install a ui or api test automation framework with the latest version of Playwright: npm init playwright@latest yarn create playwright pnpm create playwright For this blog post I'll be investigating a fourth way, the new toolset they just started using at work, bun.sh. bun create playwright What is npm, yarn, pnpm, and bun? These are called package managers. What is a package? Developing a project, you don't have to figure out how to code everything yourself. You can include in your projects outside libraries, or "packages" of code from from the public JavaScript registry npmjs.com. The problem is that these packages then need to be downloaded, installed, managed, and updated whenever they are updated. JavaScript projects can use a package manager, such as bun, to help this process. When putting together a Playwright automation framework based around JavaScript and TypeScript, Playwright uses the Node.js JavaScript runtime environment, to run its test runner, execute automation scripts, and manage its browser instances.(See Nodejs.org / About ) There is a division of labor: Node.js runs these internal functions like running tests. NPM, Yarn, PNPM, and now Bun handle the packages. Why are there so many package managers? Each has its own specialization. The original NPM is bundled already with Node.js. Yarn is a Facebook toolset that was created when NPM was found to work too slow. PNPM was created to be smaller and therefore faster. And bun was built for quick startup and installation speed, good especially if you have a CI/ CD pipeline that has a LOT of packages to install each time the tests run. NPM, released in 2010, is the Node Package Manager for Node.js, a JavaScript Runtime Environment. According to NodeJS.org ## CocoaPods Deprecation Notice for OpenTelemetry Swift DevFeed: [CocoaPods Deprecation Notice for OpenTelemetry Swift]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-20T14:05:37Z Content type: release Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [cocoapods](), [Swift](), [swift-package-manager](), [migration](), [Package manager](), [maintenance](), [Maintainers]() Tags: [cocoapods](), [maintenance](), [migration](), [opentelemetry](), [release](), [releases](), [swift](), [swift-package-manager]() ### AI overview OpenTelemetry Swift maintainers plan to deprecate CocoaPods support for the opentelemetry-swift and opentelemetry-swift-core pods as CocoaPods moves into maintenance mode. Swift Package Manager is the recommended installation method, and existing CocoaPods users are encouraged to plan migration. ### Source excerpt As it was announced via CocoaPods Support Plan and via CocoaPods Spec Repository, CocoaPods is transitioning their project to maintenance mode, and cocoapods trunk is going to be read-only in a few months. The OpenTelemetry Swift maintainers are planning to deprecate CocoaPods support for all the pods published under opentelemetry-swift and opentelemetry-swift-core. Swift Package Manager (SPM) is now the recommended and preferred installation method for all new integrations. We encourage existing CocoaPods users to begin planning a migration to SPM. ## Migrating a Flutter Application from CocoaPods to Swift Package Manager DevFeed: [Migrating a Flutter Application from CocoaPods to Swift Package Manager]() Original publisher: [Read original article]() Author: iamgirya (Яндекс) Published: 2026-07-13T07:01:51Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Flutter](), [cocoapods](), [swift-package-manager](), [iOS](), [Dart](), [macOS](), [Package manager]() Tags: [cocoapods](), [dart](), [flutter](), [ios](), [ios-development](), [macos](), [swift](), [swift-package-manager](), [swiftpm]() ### AI overview A practical guide to migrating Flutter applications from CocoaPods to Swift Package Manager. It covers dependency-graph analysis, plugin migration, dependency resolution, incremental migration, duplicate transitive dependencies, and successful iOS or macOS builds, including scripts for analysis and plugin conversion. ### Source excerpt Flutter активно движется в сторону Swift Package Manager (SPM) и, как и весь Swift-мир, постепенно отказывается от CocoaPods. Сам Flutter описывает миграцию в два шага: включить флаг flutter config --enable-swift-package-manager и запустить сборку. Если после этого приложение собирается и в консоли появляется предложение deintegrate CocoaPods -- вы счастливчик. Если нет, добро пожаловать под кат. Привет! Меня зовут Даниил Гиренко, я Flutter-разработчик в Яндекс Про. Проект по переводу нашего супераппа с CocoaPods на Swift Package Manager оказался одним из самых сложных и долгих в моей карьере программиста. Весь мой пережитый ужас опыт я решил выразить в этой статье, чтобы решившиеся на миграцию разработчики (или агенты) понимали, какие подводные камни их ждут. Буду рад, если ваш проект займёт недели, а не месяцы, как у меня. В этой статье -- полноценный гайд по миграции любого Flutter-приложения. Разберём граф зависимостей, научимся мигрировать плагины, зарезолвим зависимости и доберёмся до успешного билда. Внутри есть готовые скрипты для анализа и автоматического перевода плагинов, множественные нюансы миграции и рассказы о моих костылях. Читать далее ## How to Install MongoDB on Ubuntu: A Step-by-Step Guide for Beginners DevFeed: [How to Install MongoDB on Ubuntu: A Step-by-Step Guide for Beginners]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2026-06-06T02:40:24Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [MongoDB](), [Ubuntu](), [Linux](), [Package manager](), [Command-line interface]() Tags: [command-line](), [guide](), [how-to](), [install](), [linux](), [mongodb](), [tutorial](), [ubuntu]() ### AI overview A beginner-focused tutorial explains how to install MongoDB Community Edition on Ubuntu using the package manager. It covers importing MongoDB's GPG key, adding the package list, refreshing packages, and installing MongoDB, with notes about MongoDB 8.X and compatibility between Ubuntu versions. ### Source excerpt So you're ready to dabble with MongoDB on Linux and you've chosen Ubuntu as the variant you want to work with. Fantastic choice because you're in for a fairly easy experience that will get you up and ... The post How to Install MongoDB on Ubuntu: A Step-by-Step Guide for Beginners appeared first on DataCamp. ## NixOS 26.05 released DevFeed: [NixOS 26.05 released]() Original publisher: [Read original article]() Author: NixOS Published: 2026-05-30T07:00:00Z Content type: release Language: en Sources: [NixOS Announcements]() Topics: [Nix](), [Linux](), [releases](), [Release notes](), [systemd](), [configuration](), [modules](), [deprecated](), [Package manager]() Tags: [2026](), [accessibility](), [configuration](), [deprecated](), [end-of-life](), [gcc](), [linux](), [llvm](), [macos](), [modules](), [nix](), [nixos](), [release](), [release-notes](), [systemd](), [x86-64]() ### AI overview NixOS 26.05, named "Yarara," is publicly available as a new Linux distribution release. The announcement covers package, module, configuration, systemd initrd, platform-support, GNOME, and compiler changes, along with support timelines for NixOS 26.05 and the previous 25.11 release. ### Source excerpt Hey everyone, we are yayayayaka and jopejoe1, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 26.05 "Yarara". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2026-12-31). The old release 25.11 "Xantusia" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2026-06-30. NixOS Release Notes Highlights New Modules Backward Incompatibilities Other Notable Changes Nixpkgs Release Notes Highlights Backward Incompatibilities Other Notable Changes Nixpkgs Library Upgrade Instructions ISO Image Downloads The 26.05 release was made possible due to the efforts of 2842 contributors, who authored 59703 commits since the previous release. Highlights Our vast and routinely maintained set of packages has also been updated. This release of Nixpkgs Added 20442 new packages Updated 20641 existing packages Removed 17532 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS Added 85 new modules and 1547 configuration options Removed 25 outdated modules and 355 configuration options. systemd stage 1 Stage 1 (a.k.a. initrd) is now based on systemd by default, and the old scripted implementation is deprecated and scheduled for removal in 26.11. Deprecation of x86_64-darwin This will be the last release of Nixpkgs to support x86_64-darwin. Platform support will be maintained and binaries built until Nixpkgs 26.05 goes out of support at the end of 2026. For 26.11, due to Apple's deprecation of the platform and limited build infrastructure and developer time, we will no longer build packa ## Flutter 3.44 will make Swift Package Manager the default for iOS and macOS apps DevFeed: [Flutter 3.44 will make Swift Package Manager the default for iOS and macOS apps]() Original publisher: [Read original article]() Author: Jenn Magder Published: 2026-04-30T15:57:00Z Content type: release Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [Dependency management](), [Swift](), [iOS](), [macOS](), [Package manager](), [Command-line interface](), [Xcode]() Tags: [cli](), [cocoapods](), [dependencies](), [dependency-management](), [flutter](), [flutter-app-development](), [ios](), [macos](), [migration](), [release](), [swift](), [swift-package-manager](), [xcode]() ### AI overview Flutter 3.44 will make Swift Package Manager the default dependency manager for iOS and macOS apps, replacing CocoaPods. The Flutter CLI will migrate projects automatically, temporarily fall back to CocoaPods for unsupported plugins, and allow developers to opt out if SwiftPM causes breaking issues. ### Source excerpt Dash migration! Starting with the next stable Flutter release, 3.44, Swift Package Manager (SwiftPM) replaces CocoaPods as the default dependency manager for iOS and macOS apps. This means no more messing around with Ruby or CocoaPods installations just to get your app running! CocoaPods is officially in maintenance mode, and its registry will permanently become read-only on December 2, 2026. While existing builds will still work, no new versions or pods will be added to the trunk after this date. To ensure that your apps continue receiving dependency updates and to provide access to the Swift package ecosystem, Flutter is transitioning to Apple's supported dependency management solution: Swift Package Manager. If you've already migrated your plugin(s) to use SwiftPM, read the "Plugin developers" section below for new migration requirements. Here is how to manage the transition. App developers For app developers, the Flutter CLI handles the migration. When you run or build your iOS or macOS app, the CLI automatically updates your Xcode project to use Swift Package Manager. Check out the Flutter migration docs for app developers for more details. If your app relies on plugins that haven't adopted Swift Package Manager yet, Flutter will print a warning listing exactly which of your dependencies are unsupported. Flutter will temporarily fall back to CocoaPods for plugins that have not adopted Swift packages yet. Because CocoaPods support will eventually be removed entirely, if a plugin hasn't updated and breaks your build, file an issue with the dependency's maintainer to request Swift package support or find an alternative package. We know that migrations can sometimes hit a snag. If SwiftPM causes a breaking issue, you can temporarily disable it for your project. Open your pubspec.yaml file, navigate to the flutter section, and set enable-swift-package-manager to false under the config block: flutter: config: enable-swift-package-manager: false If you opt out, please ## Stream APIs, Swift Package Manager, Tutorial Trail Refresh, and the UWP Transition DevFeed: [Stream APIs, Swift Package Manager, Tutorial Trail Refresh, and the UWP Transition]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-03-20T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Java](), [iOS](), [Universal Windows Platform](), [Maven](), [Package manager]() Tags: [dependencies](), [ios](), [java](), [maven-plugin](), [swift-package](), [swift-package-manager](), [update]() ### AI overview Codename One adds built-in support for Java Stream APIs and Swift Package Manager integration for iOS dependencies, refreshes its written tutorial trail, and removes the UWP target from the Maven plugin in version 7.0.229. ### Source excerpt Codename One now includes built-in java.util.stream support, adds Swift Package Manager support for iOS dependencies, refreshes the written tutorial trail, and removes the UWP target from the Maven plugin in 7.0.229. ## ESP-IDF Installation Manager v0.8: Streamlined Setup for ESP-IDF Development DevFeed: [ESP-IDF Installation Manager v0.8: Streamlined Setup for ESP-IDF Development]() Original publisher: [Read original article]() Author: John Lee Published: 2026-03-02T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [cross-platform](), [Espressif](), [Package manager](), [CI/CD]() Tags: [beginner](), [blog](), [cross-platform](), [dependencies](), [eim](), [esp-idf](), [esp-idf-tool](), [espressif](), [gui](), [installation](), [linux](), [macos](), [offline](), [pipelines](), [release](), [reproducible-builds](), [toolchains](), [windows]() ### AI overview ESP-IDF Installation Manager v0.8 adds native package-manager installation methods, offline ESP-IDF installation, improved environment activation, CI/CD integration, and version management across Windows, macOS, and Linux. ### Source excerpt The ESP-IDF Installation Manager (EIM) v0.8 introduces simplified installation across Windows, macOS, and Linux through native package managers. This article covers the new release features, installation methods, offline capabilities, and headless usage for CI/CD pipelines. ## GNU Guix 1.5.0 released DevFeed: [GNU Guix 1.5.0 released]() Original publisher: [Read original article]() Author: Noé Lopez Published: 2026-01-23T14:00:00Z Content type: release Language: en Sources: [GNU Guix -- Blog]() Topics: [Package manager](), [gnu linux](), [Open Source](), [Linux](), [pull-requests]() Tags: [gnu-linux](), [images](), [installation](), [iso](), [linux](), [new-features](), [open-source](), [pull-requests](), [release](), [releases](), [update](), [virtual-machine-images]() ### AI overview GNU Guix 1.5.0 has been released with ISO installation images, virtual machine images, and tarballs for installing the package manager on GNU/Linux. The release follows three years of development and includes ecosystem changes such as a new consensus-based decision-making process, migration to Codeberg, and an annual release cycle. ### Source excerpt We are pleased to announce the release of GNU Guix version 1.5.0! The release comes with ISO-9660 installation images, virtual machine images, and with tarballs to install the package manager on top of your GNU/Linux distro, either from source or from binaries--check out the download page . Guix users can update by running guix pull . It's been 3 years since the previous release . That's a lot of time, reflecting both the fact that, as a rolling release , users continuously get new features and update by running guix pull ; but it also shows a lack of... ## postmarketOS v25.12 release upgrades Alpine Linux, package management, and mobile UIs DevFeed: [postmarketOS v25.12 release upgrades Alpine Linux, package management, and mobile UIs]() Original publisher: [Read original article]() Published: 2025-12-23T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [releases](), [Linux](), [Package manager](), [Release notes](), [Software](), [upgrade](), [Testing]() Tags: [alpine-linux](), [linux](), [packages](), [postmarketos](), [projects](), [release-notes](), [software](), [testing](), [upgrade]() ### AI overview The postmarketOS v25.12 release targets Linux enthusiasts and includes Alpine Linux 3.23, Alpine Package Keeper version 3, updated software, and mobile UI changes. The package manager now downloads packages before installation and logs changes. ### Source excerpt This release is geared mainly towards Linux enthusiasts. We are working hard on stability improvements and automated testing, but if you expect Android or iOS levels of polish, then this is not for you yet. Introduction The year is coming to a close and while you might be unwrapping other gifts shortly, we have just wrapped up the latest postmarketOS release for you. Following the epic v25.06 release where we added systemd, the most substantial change this time is less visible, but nevertheless very important: a major upgrade of the package manager (more on that below). Besides that you get once more a completely upgraded software stack representing six months of work in upstream projects and in the postmarketOS community. Software Stack Alpine Linux 3.23 As always we target the most recent Alpine release. In case of v25.12 it is the excellent Alpine Linux 3.23 and it comes with the new major version 3 of the Alpine Package Keeper, which has been released after five years (!) of development. It includes some really nice changes, such as downloading packages before installing them (which we enabled by default in postmarketOS), so that a flaky internet connection can't ever break your system again while installing updates. Another long awaited feature is logging all changes to /var/log/apk.log. See the apk3 release notes for more information. Thanks to everybody who worked on apk3 and Alpine Linux 3.23! User Interfaces (UIs) Mobile UI Versions GNOME 49 replaces GNOME 48 from v25.06. As with everything below, we recommend taking a look at upstream's release notes if you are running this UI to discover all the amazing things that made it in there! The mobile variant stays on 48.mobile.0 for this release. However we are excited to have GNOME Software upgraded from 45.3 (we had to hold it back earlier as the apk plugin couldn't be adjusted in time) to 49.2 thanks to amazing work by Angelo, Rasmus, Pablo, Sertonix, Achill and Stefan (!91416, !55). Furthermore new installat ## Blog: GPG Key Rotation for Falco Packages (2026) DevFeed: [Blog: GPG Key Rotation for Falco Packages (2026)]() Original publisher: [Read original article]() Published: 2025-12-12T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Security](), [Package manager](), [releases](), [apt]() Tags: [announcements](), [apt](), [falco](), [import](), [installation](), [releases](), [rotation](), [rsa](), [security]() ### AI overview Falco maintainers are rotating the 4096-bit RSA GPG key used to sign official RPM and DEB packages because the existing key expires on January 17, 2026. The transition uses a soft launch followed by a hard cut-over, and existing users should update their keyrings before January 12, 2026. ### Source excerpt The GPG key used to sign official Falco packages (RPM and DEB) is set to expire on January 17, 2026. To ensure the security and continuity of our software distribution, the Falco maintainers will be rotating to a new 4096-bit RSA key. We have designed a two-phase "Soft Launch" strategy to make this transition as smooth as possible, providing a one-month transition window before the old key is retired. The Rotation Plan To avoid immediate disruption, we are rolling out the new key in two distinct phases. You can follow the detailed progress in our tracking issue #3750. Phase 1: Soft Launch (Dec 12, 2025) What happens: The new GPG key has been published and added to our repository configuration. Dev Builds: Will begin using the New Key immediately. Stable Builds: No stable releases are planned for this phase. If any hotfixes are released, they will be signed with New Key as well. Key Bundle: The official key URL has been updated to serve a bundle containing both the Old (valid) and New (valid) keys. Phase 2: Hard Cut-Over (Jan 12-17, 2026) What happens: This is the maintenance window where we fully switch to the new key. Mass Resign: All existing stable packages on download.falco.org will be resigned with the New Key. Revocation: The Old Key will be officially revoked and removed from the active bundle. Impact: If you have not updated your keyring by this date, your package manager (apt or yum) will reject updates with a signature verification error. Action Items for Users We strongly recommend all users update their GPG keyring before January 12, 2026 to avoid interruption. New Users If you are installing Falco for the first time following our Install on a host (DEB,RPM) instructions, no action is required. The installation process will guide you to fetch the new key bundle, ensuring you are ready for both phases. Existing Users If you have an existing Falco installation, you must manually import the new key. We have updated the key file at our standard URL to includ ## Comparing transitive dependency version resolution in Rust and Java DevFeed: [Comparing transitive dependency version resolution in Rust and Java]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2025-12-06T02:02:51Z Content type: comparison Language: en Sources: [Java Advent Calendar]() Topics: [Java](), [Rust](), [Package manager]() Tags: [2025](), [compare](), [dependencies](), [dependency](), [java](), [rust]() ### AI overview This comparison explains how transitive dependency version resolution differs between Rust and Java. It describes dependency concepts and outlines Java's runtime classpath resolution, where class loading follows the configured classpath order. ### Source excerpt You learn by comparing to what you already know. I was recently bitten by assuming Rust worked as Java regarding transitive dependency version resolution. In this post, I want to compare the two. Dependencies, transitivity, and version resolution Before diving into the specifics of each stack, let's describe the domain and the problems that come [...] The post Comparing transitive dependency version resolution in Rust and Java appeared first on JVM Advent. ## Multi-Module Projects with Cangjie DevFeed: [Multi-Module Projects with Cangjie]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-09-02T12:39:21Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [Package manager](), [modules](), [configuration](), [Code](), [Command-line interface]() Tags: [building](), [cangjie](), [cli](), [configuration](), [huawei](), [init](), [module](), [programming](), [run](), [structure]() ### AI overview A tutorial on using the Cangjie package manager, cjpm, to create and configure multi-module projects. It covers initializing a workspace, adding executable and library modules, registering them in the workspace configuration, adding source code, building, and running the project. ### Source excerpt The Cangjie package manager cjpm is a cli tool which can be used to setup multi-module projects. A module is simply a folder with a cjpm.toml file - whilst these can also be created by hand, the cli tool simplifies the process. The approach to the setup is to create a cjpm workspace at the project root and then separate module within the workspace. It will look like this: my-project (workspace) -- module-1 -- module-2 -- module-3Create the workspace In the root of your project, initialise a workspace: # create a project folder mkdir cat-pic-downloader cd cat-pic-downloader # initialise the workspace cjpm init --workspace At this stage, your project directory will have a cjpm.toml which is the configuration for your workspace. A newly initialised workspace config will look like this. [dependencies] [workspace] build-members = [] compile-option = "" link-option = "" members = [] target-dir = "" test-members = []Add the modules To add a module to the project, use the cjpm init command but with the options to specify the type of module to create (executable, a static library or a dynamic library). Let's add a couple of modules to our sample project. # create a static lib module called 'downloader' cjpm init --type=static --path downloader # create a static lib module called 'img-processor' cjpm init --type=static --path img_processor # create an executable module called 'runner' cjpm init --type=executable --path runner By default, a newly created module has a src directory and it's own cjpm.toml to configure the module. (Static library modules will have no source code. Executable modules will have a main.cj file.) Add the modules to the workspace So that the workspace is aware of the modules we created, we need to add them to the members field of the workspace's cjpm.toml. Edit the cjpm.toml as follows. [dependencies] [workspace] build-members = [] compile-option = "" link-option = "" members = ["./runner", "./downloader", "./img_processor"] target-dir = "" test-member ## Using \`make\` to compile C programs (for non-C-programmers) DevFeed: [Using \`make\` to compile C programs (for non-C-programmers)]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-06-10T00:00:00Z Content type: tutorial Language: en Sources: [Julia Evans]() Topics: [C](), [make](), [Compiler](), [Package manager](), [gcc](), [apt](), [Xcode](), [C++]() Tags: [apt](), [building](), [c](), [c-plus-plus](), [command-line](), [compiler](), [debian](), [dependencies](), [gcc](), [libraries](), [linux](), [mac](), [make](), [packages](), [xcode]() ### AI overview A beginner-oriented guide to compiling C programs from source, covering compiler installation, dependency discovery, and build tools on Ubuntu and macOS. ### Source excerpt I have never been a C programmer but every so often I need to compile a C/C++ program from source. This has been kind of a struggle for me: for a long time, my approach was basically "install the dependencies, run make, if it doesn't work, either try to find a binary someone has compiled or give up". "Hope someone else has compiled it" worked pretty well when I was running Linux but since I've been using a Mac for the last couple of years I've been running into more situations where I have to actually compile programs myself. So let's talk about what you might have to do to compile a C program! I'll use a couple of examples of specific C programs I've compiled and talk about a few things that can go wrong. Here are three programs we'll be talking about compiling: paperjam sqlite qf (a pager you can run to quickly open files from a search with rg -n THING | qf) step 1: install a C compiler This is pretty simple: on an Ubuntu system if I don't already have a C compiler I'll install one with: sudo apt-get install build-essential This installs gcc, g++, and make. The situation on a Mac is more confusing but it's something like "install xcode command line tools". step 2: install the program's dependencies Unlike some newer programming languages, C doesn't have a dependency manager. So if a program has any dependencies, you need to hunt them down yourself. Thankfully because of this, C programmers usually keep their dependencies very minimal and often the dependencies will be available in whatever package manager you're using. There's almost always a section explaining how to get the dependencies in the README, for example in paperjam's README, it says: To compile PaperJam, you need the headers for the libqpdf and libpaper libraries (usually available as libqpdf-dev and libpaper-dev packages). You may need a2x (found in AsciiDoc) for building manual pages. So on a Debian-based system you can install the dependencies like this. sudo apt install -y libqpdf-dev libpaper-dev ## Local Speed, Smooth Deploys: Heroku Adds Support for uv DevFeed: [Local Speed, Smooth Deploys: Heroku Adds Support for uv]() Original publisher: [Read original article]() Author: Ken W. Alger Published: 2025-06-04T15:00:06Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Package manager](), [Python](), [pip](), [Deployment]() Tags: [cloud-infrastructure](), [deployment](), [developer-tools](), [efficiency](), [engineering](), [heroku](), [package-management](), [packages](), [python]() ### AI overview Heroku adds support for uv, a Python package manager positioned as a faster alternative to pip. The article discusses Python package-management history and describes setting up a project for Heroku deployment with uv. ### Source excerpt Ah, another day, another deep dive into the ever-evolving world of Python development! Today, let's talk about something near and dear to every Pythonista's heart - managing those crucial external packages. For years, pip has been our trusty companion, the workhorse that gets the job done. But the landscape is shifting, and a new contender [...] The post Local Speed, Smooth Deploys: Heroku Adds Support for uv appeared first on Heroku. ## A New Nx Experience for TypeScript Monorepos and Beyond DevFeed: [A New Nx Experience for TypeScript Monorepos and Beyond]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2025-01-29T00:00:00Z Content type: release Language: en Sources: [Juri Strumpflohner]() Topics: [TypeScript](), [Developer experience](), [Package manager]() Tags: [bun](), [developer-experience](), [monorepo](), [monorepo-tools](), [npm](), [npm-workspaces](), [nx](), [pnpm](), [release](), [tooling](), [typescript]() ### AI overview Nx introduces a workspaces-based setup that combines NPM, Yarn, PNPM, or Bun workspaces with TypeScript project references for monorepos. The article explains the expected performance, memory-use, and editor-support benefits, while noting that the feature is initially behind a flag. ### Source excerpt Discover how Nx's new workspaces setup combines package managers with TypeScript project references for better performance and developer experience in monorepos. ## How to Use pnpm on Heroku DevFeed: [How to Use pnpm on Heroku]() Original publisher: [Read original article]() Author: Colin Casey Published: 2024-07-19T02:12:00Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [pnpm](), [Heroku](), [Package manager](), [Node.js](), [npm](), [Command-line interface](), [Express](), [Git]() Tags: [buildpacks](), [cli](), [dependencies](), [developer-tools](), [development](), [engineering](), [express](), [git](), [heroku](), [how-to](), [install](), [integrity](), [node](), [node-js](), [npm](), [packages](), [pnpm]() ### AI overview This tutorial explains how to use pnpm as an alternative to npm for Node.js applications deployed on Heroku. It covers pnpm's content-addressable store, dependency installation workflow, Corepack-based installation, version pinning, and creating a sample Express application. ### Source excerpt What is pnpm? Pnpm is a fast, disk-efficient Node package manager used as an alternative to npm. The Heroku Node.js buildpack now supports pnpm. Early Node.js application owners who've taken advantage of pnpm support have seen 10-40% faster install times compared to NPM on Heroku deployments. It's an excellent choice for managing packages in the [...] The post How to Use pnpm on Heroku appeared first on Heroku. ## Impact of final JCenter shutdown on Gradle Plugin Portal DevFeed: [Impact of final JCenter shutdown on Gradle Plugin Portal]() Original publisher: [Read original article]() Author: Louis Jacomet Published: 2024-07-05T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Package manager](), [configuration]() Tags: [analysis](), [blog-post](), [build](), [dependencies](), [gradle](), [jfrog](), [maven-central](), [proxy]() ### AI overview The article analyzes the impact of JCenter becoming a permanent redirect to Maven Central on the Gradle Plugin Portal and Gradle builds. It explains the portal's move from acting as a JCenter proxy to a Maven Central proxy and identifies plugin and transitive-dependency resolution failures that users may encounter. ### Source excerpt ℹ Update on July 15, 2024 We have found errors causing false positive in failed plugin resolution. 4 plugins have been removed from the list, resulting in 9 removed dependencies. We also added 105 plugins that depend on one or more affected plugins. These will fail to resolve transitively. Not taking exclude into account caused the first change, the second one came from not taking plugin dependencies into account. Now that JFrog has confirmed that JCenter will become a permanent redirect to Maven Central, we felt that it was important for the Gradle Plugin Portal users to understand the impact of that decision on the portal and their builds. This post follows our report after JCenter redirected to Maven Central for a day. Users still directly using JCenter should also refer to our original blog post about the changes in JCenter and their impact on Gradle builds in general. Upcoming Plugin Portal changes JCenter will become a permanent redirect to Maven Central. As a consequence, the Gradle Plugin Portal will no longer act as a JCenter proxy and will instead become a Maven Central proxy. The Gradle Plugin Portal will continue to return redirects (303 See Other) for artifact queries it cannot serve. Starting July 15, 2024, these redirects will be towards Maven Central instead of JCenter. This change might impact existing Gradle builds: Build using plugins with dependencies that are exclusively available on JCenter will fail to resolve. Builds configured to use the Gradle Plugin Portal as a regular artifact repository (which is not recommended) may be impacted. For more information, refer to our original blog post. We aim to document the potential impact on Gradle plugins provided by the Plugin Portal. Read our analysis below to learn how to minimize the impact on your builds. Impact analysis We have performed two major analyses: For all the plugins known to the Gradle Plugin Portal, determine which ones would fail to resolve if their transitive dependencies are resol ## Nix Weekly Recap: 2024-06-09 DevFeed: [Nix Weekly Recap: 2024-06-09]() Original publisher: [Read original article]() Published: 2024-06-09T00:00:00Z Content type: news Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [releases](), [Package manager]() Tags: [community](), [news](), [packages](), [recap](), [regular](), [tools](), [weekly]() ### AI overview The June 9, 2024 Nix weekly recap covers a retrospective meeting for the NixOS 24.05 release, a call for social media support on the Marketing team, Brioche package manager news, security fixes, and new packages added to Nixpkgs. ### Source excerpt NixOS 24.05 retrospective, marketing team call for social media support, and the introduction of Brioche. ## How to transition to secure container images with new migration guides DevFeed: [How to transition to secure container images with new migration guides]() Original publisher: [Read original article]() Published: 2024-05-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [migration](), [container images](), [container-security](), [APK](), [Dockerfile](), [Package manager](), [Bash](), [Zsh](), [Debian]() Tags: [and-best-practices](), [apk](), [base-images](), [bash](), [best-practices](), [build](), [chainguard](), [chainguard-images](), [container](), [container-based-application](), [container-images](), [container-security](), [container-security-strategy](), [cves](), [debian](), [dependencies](), [docker-hub-image](), [dockerfiles](), [guides](), [how-to](), [image-migration](), [migration](), [migration-guides](), [python-image](), [secure-container-image](), [secure-container-images]() ### AI overview This guide explains how to migrate container images to Chainguard Images for smaller image sizes, fewer vulnerabilities, and continuous maintenance. It covers using -dev images for shells and package managers, installing bash or zsh when needed, searching for packages with apk, and adapting Dockerfiles and entrypoint scripts. ### Source excerpt Struggling to adopt secure container images? Our new migration guides provide step-by-step instructions and best practices for a smooth transition. ## How to enable Debian 12 Backports repository DevFeed: [How to enable Debian 12 Backports repository]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-11T11:02:39Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Debian](), [Package Management](), [apt](), [Package manager](), [Linux]() Tags: [apt](), [apt-cache](), [debian](), [debian-linux](), [dependencies](), [easy](), [how-to](), [install](), [linux](), [package-management](), [packages](), [software-packages]() ### AI overview A tutorial on enabling and using the Debian 12 Bookworm Backports repository. It covers configuring the repository, updating package lists, searching for packages, installing selected backported packages, listing installed backports, and removing them. ### Source excerpt The Debian Linux 12 backports repository offers updated versions of software packages for Debian Stable releases. These packages are sourced from Testing (and sometimes Unstable) branches of Debian, and then optimized and recompiled to function on the current Stable release, such as Bookworm. Let us see how to install and use Debian Linux 12 "Bookworm" Backports repository. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to enable Debian 12 Backports repository appeared first on nixCraft. ## Nix Weekly Recap: 2024-05-11 DevFeed: [Nix Weekly Recap: 2024-05-11]() Original publisher: [Read original article]() Published: 2024-05-11T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Package manager](), [Maintainers](), [Wiki](), [Pull Request](), [Google](), [Google Calendar]() Tags: [announcements](), [community](), [contributors](), [documentation](), [governance](), [packages](), [pull-request](), [recap](), [repository](), [security](), [weekly]() ### AI overview The May 11, 2024 Nix weekly recap covers the public preview of Lix, a Nix fork focused on correctness and usability; applications for the Nix Constitutional Assembly; efforts to update links to the new NixOS wiki; documentation office hours and maintainer onboarding; security fixes; and newly added packages. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## How Apollo Manages Swift Packages in a Monorepo with Git Subtrees DevFeed: [How Apollo Manages Swift Packages in a Monorepo with Git Subtrees]() Original publisher: [Read original article]() Author: Zach FettersMoore Published: 2024-01-30T07:45:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [monorepo](), [Swift](), [swift-package-manager](), [Git](), [Submodules](), [Library](), [Package manager](), [iOS](), [Code](), [Development]() Tags: [development](), [git](), [ios](), [library](), [mobile](), [monorepo](), [packages](), [pull-requests](), [submodules](), [swift](), [swift-package](), [swift-package-manager](), [testing]() ### AI overview The article describes Apollo iOS's challenges with managing multiple Swift Package Manager library targets in a monorepo. It explains the goal of distributing smaller, independently versioned packages while preserving an efficient shared development and testing workflow, and discusses Git submodules as one approach and its operational drawbacks. ### Source excerpt The monorepo is a common structure for many software projects, and Apollo iOS is no different. Our project was structured in a single repo containing many different Swift Package Manager (SPM) library targets, along with test code and code only used as part of development. This presents a few problems however, one being that when a user adds the SPM package as a dependency, it will pull down all of the code and files in the repo, even though most of them aren't needed. [Next page]()