# Package Management Systems and tools for discovering, installing, upgrading, uninstalling, and optionally configuring software packages. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Add the 007revad Community Package Source to Synology DSM DevFeed: [How to Add the 007revad Community Package Source to Synology DSM]() Original publisher: [Read original article]() Author: Rob Andrews Published: 2026-08-10T16:00:01Z Content type: tutorial Language: en Sources: [NAS Compares]() Topics: [Synology](), [synology nas](), [Package Management](), [Script](), [Homelab](), [Open Source](), [Hardware](), [Transcodings](), [GitHub](), [Network]() Tags: [007revad](), [007revad-mod](), [007revad-synology](), [airconnect](), [aqc-unlock](), [command-line](), [compatibility](), [configuration](), [data-recovery](), [dave-russell](), [documentation](), [drive](), [dsm-7](), [github](), [hardware](), [homebridge](), [homelab](), [librespeed](), [nas](), [nas-apps](), [nas-mods](), [nas-software](), [nascompares](), [network](), [network-attached-storage-nas](), [ookla-speedtest](), [open-source](), [openspeedtest](), [package-management](), [plex](), [projects](), [ssh](), [storage](), [synocr](), [synology](), [synology-007revad](), [synology-10gbe](), [synology-2-5g-driver](), [synology-2026](), [synology-2027](), [synology-5gbe-driver](), [synology-add-ons](), [synology-apps](), [synology-community](), [synology-community-packages](), [synology-container-manager](), [synology-nas](), [uncategorised]() ### AI overview This tutorial explains how to add 007revad's unofficial community package source to Synology DSM Package Center. It describes how the source makes selected community packages easier to discover, install, and update, while noting that package availability depends on the NAS model, CPU architecture, and DSM version. ### Source excerpt A New and Easier Way to Mod Your Synology NAS Synology's gradual shift towards business and enterprise users has changed what some home, enthusiast and homelab users can do with DSM, particularly when it comes to 3rd-party drives, SSDs, network adapters, hardware transcoding and other unofficial modifications. Community-developed scripts have helped restore or extend many [...] ## PowerShell PSResource Roadmap and Best Practices DevFeed: [PowerShell PSResource Roadmap and Best Practices]() Original publisher: [Read original article]() Author: Sydney Smith Published: 2026-05-20T20:56:10Z Content type: article Language: en Sources: [PowerShell Team]() Topics: [PowerShell](), [Package Management](), [Security](), [supply-chain-security](), [Automation](), [configuration](), [NuGet]() Tags: [automation](), [best-practices](), [enterprise](), [infrastructure](), [microsoft](), [nuget](), [package-management](), [powershell](), [security](), [supply-chain]() ### AI overview PowerShell PSResourceGet best practices for secure package management, including repository trust, validation, approval, governance, and enterprise use of Microsoft Artifact Registry and OCI-compliant registries. The article also outlines roadmap investments aimed at secure-by-default package management. ### Source excerpt PowerShell is a critical automation and configuration platform across enterprises--and as that automation grows, how you source, validate, and distribute PowerShell packages becomes just as important as the scripts themselves. Modern security guidance increasingly treats package feeds as part of the software supply chain. For PowerShell, that means being deliberate about which repositories you trust, [...] The post PowerShell PSResource Roadmap and Best Practices appeared first on PowerShell Team. ## Chainguard brings first-party RHEL 9 and RHEL 10 RPM support to Chainguard OS, joins FINOS DevFeed: [Chainguard brings first-party RHEL 9 and RHEL 10 RPM support to Chainguard OS, joins FINOS]() Original publisher: [Read original article]() Published: 2026-05-11T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard os](), [chainguard containers](), [Security](), [Critical Infrastructure](), [Package Management](), [Open Source](), [Cloud Native Ecosystem](), [Resilience](), [APK](), [Linux]() Tags: [chainguard](), [chainguard-containers](), [chainguard-finserv](), [chainguard-os](), [cloud](), [cloud-native](), [compatibility](), [compliance](), [container](), [container-images](), [containers](), [critical-infrastructure](), [cve](), [dependencies](), [hardening](), [images](), [linux](), [make](), [mythos](), [open](), [open-source](), [project-glasswing](), [rhel](), [rhel-10](), [rhel-9]() ### AI overview Chainguard announces first-party RHEL 9 and RHEL 10 RPM compatibility for packages in Chainguard Containers built on Chainguard OS. The company also announces that it is joining FINOS to support open source collaboration in financial infrastructure. ### Source excerpt Chainguard adds first-party RHEL 9/10 RPM compatibility and joins FINOS, helping financial institutions modernize securely for the AI-driven threat era. ## Python Environments Extension for VS Code- April Update DevFeed: [Python Environments Extension for VS Code- April Update]() Original publisher: [Read original article]() Author: Vedha Ranganathan Published: 2026-04-27T20:07:30Z Content type: release Language: en Sources: [Microsoft Python Engineering]() Topics: [Python](), [Extension](), [Visual Studio Code](), [Package Management](), [Conda](), [Poetry](), [ssh]() Tags: [2026](), [conda](), [crash](), [extension](), [microsoft](), [poetry](), [python](), [recovery](), [release](), [remote](), [ssh](), [terminal](), [update](), [vs-code]() ### AI overview Microsoft's April 2026 release update for the Python Environments extension in Visual Studio Code describes faster startup and environment resolution, narrower workspace scanning, improved crash recovery, a Conda environment fix, automatic package-list refreshes, and multi-project terminal support. ### Source excerpt The April 2026 release update includes the Python Environments extension... Keep on reading to learn more! The post Python Environments Extension for VS Code- April Update appeared first on Microsoft for Python Developers Blog. ## Snyk and uv, Better Together DevFeed: [Snyk and uv, Better Together]() Original publisher: [Read original article]() Author: Ryan Searle Published: 2026-02-24T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Package Management](), [Python](), [supply-chain-security](), [AI Development](), [Vulnerabilities](), [JSON](), [Maintainers](), [GitHub](), [toolchain](), [pip](), [Poetry]() Tags: [ai](), [ai-development](), [application-security](), [awareness](), [blog](), [code-security](), [developer](), [development](), [devrel](), [enablement](), [executive](), [github](), [interest](), [json](), [maintainers](), [package-management](), [pmm](), [python](), [related-content](), [sbom](), [security](), [supply-chain-security](), [toolchain](), [vulnerabilities]() ### AI overview Snyk and uv have partnered to combine uv's high-performance Python package management with supply chain security. Their collaboration adds native CycloneDX SBOM export to uv, enabling Snyk vulnerability and license-compliance testing for uv-managed projects. ### Source excerpt Snyk and uv have teamed up to provide high-performance package management with native security for Python-based AI development. Build, install, and secure your AI-native applications from inception with Snyk's native support for the uv ecosystem. ## Meet Guix at FOSDEM DevFeed: [Meet Guix at FOSDEM]() Original publisher: [Read original article]() Author: Ludovic Courtès Published: 2026-01-22T13:00:00Z Content type: article Language: en Sources: [GNU Guix -- Blog]() Topics: [FOSDEM](), [Package Management](), [reproducibility](), [systems]() Tags: [ci-cd](), [community](), [fosdem](), [guix-days](), [package-management](), [reproducibility](), [systems](), [talks]() ### AI overview The Guix community will participate in FOSDEM with talks on package management and reproducibility, bioinformatics workflows, Guile development, build systems, functional reactive programming, container images, and GNU/Hurd. About sixty Guix contributors will then gather for Guix Days on February 2-3. ### Source excerpt It's that time of the year again: next week is FOSDEM time! As in previous years , many Guix people will be in Brussels. Right after FOSDEM, about sixty of us will gather on February 2-3 for the Guix Days! First things first: Guix presence at FOSDEM. On Saturday, January 31st : In Name resolution in package management systems -- A reproducibility perspective , Gábor Boskovits will look will look at how several package managers refer to packages and how this affects reproducibility. Simon Tournier will... ## JavaScript's dependency ecosystem needs stronger supply-chain security and package management DevFeed: [JavaScript's dependency ecosystem needs stronger supply-chain security and package management]() Original publisher: [Read original article]() Author: September Published: 2025-09-17T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [JavaScript](), [Package Management](), [npm](), [Linux]() Tags: [dependency-management](), [javascript](), [linux](), [npm](), [reproducible-builds](), [supply-chain]() ### AI overview This opinion article argues that JavaScript's dependency ecosystem should respond to supply-chain attacks by reducing sprawling dependency trees and adopting stronger trust, package-signing, distribution, and reproducible-build practices. It also proposes a standard library and more consolidated packages. ### Source excerpt In the wake of the largest supply-chain attack in history, the JavaScript community could have a moment of reckoning and decide: never again. As the panic and shame subsides, after compromised developers finish re-provisioning their workstations and rotating their keys, the ecosystem might re-orient itself towards solving the fundamental flaws that allowed this to happen. After all, people have been sounding the alarm for years that this approach to dependency management is reckless and dangerous and broken by design. Maybe this is the moment when the JavaScript ecosystem begins to understand the importance and urgency of this problem, and begins its course correction. It could leave behind its sprawling dependency trees full of micro-libraries, establish software distribution based on relationships of trust, and incorporate the decades of research and innovation established by more serious dependency management systems. Perhaps Google and Mozilla, leaders in JavaScript standards and implementations, will start developing a real standard library for JavaScript, which makes micro-dependencies like left-pad a thing of the past. This could be combined with a consolidation of efforts, merging micro-libraries into larger packages with a more coherent and holistic scope and purpose, which prune their own dependency trees in turn. This could be the moment where npm comes to terms with its broken design, and with a well-funded effort (recall that, ultimately, npm is GitHub is Microsoft, market cap $3 trillion USD), will develop and roll out the next generation of package management for JavaScript. It could incorporate the practices developed and proven in Linux distributions, which rarely suffer from these sorts of attacks, by de-coupling development from packaging and distribution, establishing package maintainers who assemble and distribute curated collections of software libraries. By introducing universal signatures for packages of executable code, smaller channels and ## Cangjie -- a programming language from Huawei DevFeed: [Cangjie -- a programming language from Huawei]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-08-19T07:37:53Z Content type: opinion Language: en Sources: [Snapp Mobile - Medium]() Topics: [Programming language](), [huawei](), [Programming](), [Code](), [Embedded Systems](), [Cross-Compilation](), [Mobile](), [cloud-computing](), [Package Management](), [debug](), [Testing](), [ide]() Tags: [architectures](), [bytecode](), [cangjie](), [china](), [cloud](), [cross-compilation](), [debugging](), [developers](), [development](), [embedded-systems](), [huawei](), [huawei-developers](), [language](), [mobile](), [package-management](), [programming](), [programming-language](), [programming-languages](), [tools]() ### AI overview This article examines Cangjie, an open-sourced programming language from Huawei. It describes Cangjie as a C-like language with features associated with Swift and Kotlin, support for embedded systems, mobile development, and cloud architectures, interoperability with C and Python, JVM bytecode compilation, cross-compilation, and integrated developer tools. The article suggests Huawei created it to gain more control over its language roadmap and consolidate development skills across products. ### Source excerpt Cangjie -- a programming language from Huawei Huawei have been busy. Last month they open-sourced a programming language that is looking pretty interesting. Whilst you might not be writing in Cangjie next week, it's good to see what one of the world's largest technology companies is doing such that they have created a new programming language. TL;DR Cangjie is a C-like programming language that feels more like Swift/Kotlin than Java/C# or JavaScript/Typescript. The idea is for Cangjie to become the common programming language to be used throughout Huawei. Cangjie can be used for embedded systems, mobile development, server-side cloud architectures. It supports a variety of programming paradigms (function, OO, procedural), compilation and integration options. Cangjie can call C libraries (and be called from C), use Python libraries and even compile to JVM bytecode. Cangjie supports language extension to create lightweight DSLs. Primarily Cangjie programs are compiled into machine code -- this include cross compilation which mean they can run natively on different computer architectures. Cangjie comes with a set of in-built tools for developers such as package management, debugging, testing and IDE integration. Cangjie is openly available since this month and is in version 0.53.13. Why create a new language? Simply put, Cangjie gives Huawei a level of control and an economy of scale that they cannot get from other languages. Most mainstream languages are driven predominantly by teams in USA and Europe. It is hard to influence the road map for these languages -- especially for those tightly controlled by corporations (e.g. Java/Kotlin/Swift). Furthermore, consolidating programming skills could be a big efficiency gain for Huawei -- engineers working on products ranging from routers to petabyte storage to cloud computing and mobile devices can coalesce around one language and toolset. Show me some code I won't go into any detail here so this is just to satisfy your curiosit ## How to Identify the Package Manager of a Linux System DevFeed: [How to Identify the Package Manager of a Linux System]() Original publisher: [Read original article]() Author: Umara Mushtaq Published: 2025-07-14T02:13:11Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Package Management](), [Linux](), [apt](), [Bash](), [Scripting, bash](), [Ubuntu](), [Automation](), [Debian](), [Arch Linux](), [dnf](), [Fedora](), [pacman]() Tags: [apt](), [automation](), [bash](), [debian](), [dependency](), [dnf](), [efficiency](), [errors](), [how-to](), [installation](), [linux](), [linux-how-to](), [package-management](), [package-management-scripting-apt-dnf-pacman-snap-yum](), [pacman](), [scripting](), [snap](), [ubuntu]() ### AI overview This tutorial explains how to identify the package manager used by a Linux system. It covers inferring the manager from the distribution, checking distribution metadata with /etc/os-release or lsb_release, verifying an installed manager with which, and using Bash scripts to detect package managers in automated or multi-distribution environments. ### Source excerpt Learn different ways to guess or identify the default package manager of a Linux system. The post How to Identify the Package Manager of a Linux System first appeared on Baeldung on Linux. Related Stories How to Check for Available Package Updates in Linux How to Properly Install Valgrind? Background Jobs in a Loop in Bash ## netlab 1.9.6: Static Routes to Default Gateways DevFeed: [netlab 1.9.6: Static Routes to Default Gateways]() Original publisher: [Read original article]() Published: 2025-03-25T07:25:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [gateway](), [Python](), [Ubuntu](), [Networks](), [Package Management](), [upgrade]() Tags: [bug-fixes](), [dependencies](), [gateway](), [netlab](), [networks](), [python](), [release](), [ubuntu]() ### AI overview netlab 1.9.6 fixes installation problems caused by Python dependency conflicts on Ubuntu 24.04. The release also adds default gateways as valid next hops for static routes, improves IPv6 default-gateway processing, sets a 9500 MTU for libvirt bridge networks, and supports specifying Juniper vMX license files through device or node variables. ### Source excerpt Last week, I had to push out netlab release 1.9.6 to address a particularly nasty Python dependency hell to make netlab work (again) on Ubuntu 24.04 (more details). The release also brought these goodies (and a bunch of bug fixes): Add default gateway (including anycast- and VRRP gateway )as a valid next-hop for static routes Rewrite the default gateway processing and add IPv6 default gateways on links without anycast or VRRP gateways Set libvirt MTU to 9500 on bridge-based networks to avoid the "transparent fragmentation" on Linux bridges. Use device- or node variables to specify the Juniper vMX license file. Read more ... ## From XAMPP to Ephemeral Postgres: Where "Works on My Machine" Has Led Us DevFeed: [From XAMPP to Ephemeral Postgres: Where "Works on My Machine" Has Led Us]() Original publisher: [Read original article]() Author: Andrew Tate Published: 2025-02-27T00:51:30Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Web Development](), [XAMPP](), [MySQL](), [PHP](), [configuration](), [Databases](), [Package Management](), [toolchains](), [Open Source]() Tags: [apache](), [coding](), [community](), [configuration](), [database](), [databases](), [debugging](), [dependencies](), [developers](), [development](), [environment-variables](), [installations](), [libraries](), [local](), [mysql](), [open-source](), [package-management](), [php](), [servers](), [source](), [systems]() ### AI overview This article looks back at local web development in the 1990s, when developers manually installed and configured Apache, PHP, and databases such as MySQL and Postgres. It describes environment drift, dependency and version conflicts, difficult database setup, manual configuration, and the technical understanding that these constraints encouraged. ### Source excerpt "It works on my machine" is now a trope--a horror story to tell young developers (or AI coding models) about what it was like to build without today's stack. Like all clichés, it was once true. Hodgepodge local installs, no containers, and massive environment drift were challenges... ## HarmonyOS App Development 101 DevFeed: [HarmonyOS App Development 101]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-01-18T23:23:13Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [App](), [Development](), [ide](), [huawei](), [SDK](), [Tooling](), [jetbrains](), [Package Management](), [Testing](), [Open Source]() Tags: [android](), [app](), [app-development](), [apps](), [code-completion](), [debug](), [deployment](), [development](), [harmony-os](), [huawei](), [ide](), [jetbrains](), [open-source](), [package-management](), [programming-languages](), [refactoring](), [sdk](), [testing](), [tools](), [ui](), [ui-framework]() ### AI overview An overview of HarmonyOS Next app development, covering the Huawei-based DevEco Studio IDE, project configuration, SDK versions, modules, and common development features. The article also outlines programming languages, UI frameworks, build tools, package management, execution, debugging, testing, and profiling. ### Source excerpt Huawei have taken a big step in moving away from the Android platform with the launch of new devices running HarmonyOS Next. This is a brand new operating system that had been design specifically for devices. This means it is lightweight, supports a range of device types, is modular and extensible. In this article we aim to give you an overview of what is available to developers wishing to build apps on this new platform. To that end, we will be looking at the following topics: The IDE Programming Languages UI Framework Build Tools Package Management Running code (devices/emulators) Debugging Testing Profiling Other cool stuff If you are curious about the Harmony platform, its Open Source foundations (OpenHarmony) and its global reach (Oniro), we have written about it here. The IDE The development environment for Harmony apps is currently a Huawei-based IDE which is based on the JetBrains IDE platform. The good news is that JetBrains offers a world-class IDE platform and it makes for a very solid development experience for Harmony apps. For those, wanting to keep to the Open Source side of Harmony (OpenHarmony and Oniro), you are out of luck right now. DevEco Studio is proprietary, albeit free to use software. Let's look at a couple of IDE features -- these should not surprise you but hopefully demonstrates that the platform is already in a good place (as far as IDEs go). Project Creation Creating a project will look familiar already for many. There are a few project templates to choose from to bootstrap your project. New Project Templates You will also then need to configure a couple of options -- a couple of notes on these (which could probably be expanded into a separate article). Firstly, the bundle name is used for app signing and identity. Secondly, an app supports a single SDK version. (The latest SDK version is 13, however version 11 is still widely used.) Thirdly we can specify the module name. The default ('entry') isn't very descriptive. If you have a singl ## Nix Weekly Recap: 2024-05-05 DevFeed: [Nix Weekly Recap: 2024-05-05]() Original publisher: [Read original article]() Published: 2024-05-05T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Package Management](), [Homebrew](), [Tooling](), [Gitea]() Tags: [announcements](), [cncf](), [community](), [governance](), [homebrew](), [package-management](), [recap](), [tooling](), [weekly]() ### AI overview This weekly recap covers governance changes in the Nix ecosystem, including Eelco Dolstra's departure from the NixOS Foundation Board and plans for a constitutional assembly. It also highlights the Aux fork, Brew-nix for packaging Homebrew casks with Nix, Noshell, Buildbot-nix support for Gitea, a Framework partnership, Nix-inst, and a new moderator. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## Reimagining the Linux distro with Wolfi DevFeed: [Reimagining the Linux distro with Wolfi]() Original publisher: [Read original article]() Published: 2024-02-21T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Linux](), [chainguard](), [container-security](), [Security](), [Package Management](), [APK](), [Open Source]() Tags: [apk](), [apko](), [chainguard](), [chainguard-images](), [container-security](), [cve](), [linux](), [melange](), [open-source](), [package-management](), [secure-container-images](), [security](), [vulnerabilities](), [wolfi]() ### AI overview The article explains why Chainguard created Wolfi, a minimal Linux distribution designed for modern container use. It describes the roles of Melange for building APK packages and Apko for assembling reproducible container images, along with Wolfi's security advisory and vulnerability-management capabilities. ### Source excerpt Discover Wolfi: Chainguard's answer to modern container security, creating minimal, secure Linux distributions for today's needs. ## Wolfi: a new paradigm in Linux for containers DevFeed: [Wolfi: a new paradigm in Linux for containers]() Original publisher: [Read original article]() Published: 2024-01-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Linux](), [Containers](), [Package Management](), [container images](), [Security]() Tags: [apk](), [apko](), [chainguard](), [chainguard-images](), [containers](), [linux](), [melange](), [package-management](), [security](), [wolfi]() ### AI overview Wolfi is a minimal Linux distribution designed for containerized applications. The article describes its focus on efficiency, security, rapid updates, reproducible APK-based package management, and container image creation through melange and apko. ### Source excerpt Wolfi is a Linux distribution built specifically for containerized applications. See how it can speed up your development process. ## My Mac Dev Setup and Favorite Tools DevFeed: [My Mac Dev Setup and Favorite Tools]() Original publisher: [Read original article]() Author: Chris Hager Published: 2024-01-12T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [Development](), [Tool](), [Command-line interface](), [Shell](), [Terminal](), [backups](), [passwords](), [Homebrew](), [Package Management](), [Encryption](), [App](), [Obsidian]() Tags: [backup](), [csv](), [database](), [dev](), [dev-setup](), [developer-setup](), [editor](), [encryption](), [homebrew](), [iterm2](), [mac](), [macos](), [setup](), [tools]() ### AI overview A practical guide to setting up a Mac for software development, covering system security, backups, password management, developer tools, favorite applications, terminal use, and keyboard shortcuts. ### Source excerpt How I setup and use my computer and tools for development. I wrote this mostly as a guide for myself, for the next time I setup a computer, and hope it might be useful to others too. I'd love to hear your thoughts, ideas and additional tips in the comments below! Related: How I setup my Terminal and Bash. Contents Mac setup General system setup Favorite apps Keyboard shortcuts Application shortcuts Arranging windows Browser Terminal & Shell Docker for Node. ## An Introduction to Swift Package Manager and how it works DevFeed: [An Introduction to Swift Package Manager and how it works]() Original publisher: [Read original article]() Author: prateek arora Published: 2023-04-11T05:00:35Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [swift-package-manager](), [Package manager](), [Package Management](), [Swift](), [Xcode](), [Open Source](), [iOS](), [Linux](), [tvOS]() Tags: [apple](), [cocoapods](), [dependencies](), [introduction](), [ios](), [linux](), [macos](), [open-source](), [package-management](), [packages](), [swift](), [swift-package](), [swift-package-manager](), [xcode]() ### AI overview An introductory tutorial explains Swift Package Manager (SPM), its role in downloading, compiling, and linking Swift dependencies, and its integration with Swift. It compares SPM with third-party options such as CocoaPods and Carthage, outlines supported platforms and requirements, and describes advantages and limitations. ### Source excerpt What is a package Manager? A package manager or package-management system is a collection of software tools that automates the process of installing, upgrading, configuring, and removing computer programs for a computer in a consistent manner. or A package manager deals with packages, distributions of software and data in archive files. Packages contain metadata, such as the software's name, description of its purpose, version number, vendor, checksum (preferably a cryptographic hash function), and a list of dependencies necessary for the software to run properly. What is Swift Package Manager (SPM) As per official Apple Swift Documentation: "The Swift Package Manager is a tool for managing the distribution of Swift code. It's integrated with the Swift build system to automate the process of downloading, compiling, and linking dependencies." The Package Manager is included in Swift 3.0 and above. Why do we need Swift Package Manager? Though we have multiple other ways to manage the dependencies like cocoa pods, Carthage etc. then why is there a need to use SPM? The answer is both cocoa pods and Carthage are third-party package managers, which eventually leads to extra code and efforts one has to put in order to utilise these third-party package managers. For example: For cocoa pods, we need to have a pod framework to be installed, which then needs ruby, gem file or brew in order to install pods. But then SPM comes inbuilt with XCode, so there won't be extra effort and extra files that will be getting added once we use SPM. System Requirement SwiftPM is compatible with macOS, iOS, tvOS and Linux For macOS, you need XCode 11 and above. For Linux, you have to install it manually or use swiftenv. Advantages SwiftPM is open-source like Cocoapods. It may be challenging or fast to contribute but it is possible. Ease of managing dependency's dependencies. If a dependency relies on another dependency, the Swift Package manager will handle it for you. Ease of resetting, manag ## The Road To 1.0 DevFeed: [The Road To 1.0]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2022-07-14T16:41:00Z Content type: opinion Language: en Sources: [Red]() Topics: [Red](), [modules](), [Package Management](), [Concurrency](), [toolchain](), [Compiler]() Tags: [announce](), [build](), [compilation](), [concurrency](), [modular](), [package-management](), [toolchain]() ### AI overview The Red project presents an updated plan focused on completing its core language and reaching version 1.0. The plan includes upgrading the 32-bit implementation, formalizing the language specification, adding modules and package management, defining a concurrency model, and preparing a new toolchain. ### Source excerpt You cannot have missed that in the last months (and even last years), our overall progress has slowed down drastically. One of the main reasons is that we have spread our limited resources chasing different objectives while making little progress on the core language. That is not satisfying at all and would bring us most likely to a dead-end as we exhaust our funding. We have spent the last weeks discussing about how to change that. This is our updated action plan. From now on, our only focus will be to finish the core language and bring it to the much-awaited version 1.0. We need to reach that point in order to kickstart a broader adoption and provide us and our users a stable and robust foundation upon which we can build commercial products and services necessary for sustainability. Given the complexities involved in completing the language and bringing an implementation that can run on modern 64-bit platforms, we have devised a two-stage plan. Upgrade the current 32-bit Red implementation 👉 Language specification It is now time to do so in order to clean-up some semantic rules and address all possible edge cases which will help fulfill our goals of implementation robustness and stability. The process of writing down the complete language specs will result in dropping some features that we currently have that end up being problematic or inconsistent. OTOH, we might add some new features that will need to be implemented for 1.0. 👉 Modules We need a proper module system in order to be scalable. We also need to have a proper package management system which will be tied to a central repo where we can gather third-party libraries. That would also enable modular/incremental compilation (or encapping) which will be most probably supported in the self-hosted toolchain. 👉 Concurrency We need a proper model for concurrent execution in order to leverage multicore architectures. We will define one and make a prototype implementation in the 32-bit version. 👉 Toolchain Before s ## Setup your Workstation for JavaScript Development DevFeed: [Setup your Workstation for JavaScript Development]() Original publisher: [Read original article]() Published: 2019-04-26T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Development](), [JavaScript](), [Node.js](), [npm](), [modern web development](), [Git](), [Package Management](), [Tooling](), [Angular]() Tags: [angular](), [development](), [git](), [javascript](), [node-js](), [npm](), [package-management](), [tooling](), [workstation]() ### AI overview This tutorial explains how to set up a workstation for JavaScript development, with an emphasis on modern web development and Angular. It introduces Git for version control and Node.js with npm for server-side JavaScript and frontend tooling, including installation and verification guidance. ### Source excerpt Lorem ipsum dolor sit amet ## How to Create a Free Static Website and Blog with Jekyll DevFeed: [How to Create a Free Static Website and Blog with Jekyll]() Original publisher: [Read original article]() Published: 2018-07-27T01:59:05Z Content type: tutorial Language: en Sources: [Emily Kager]() Topics: [Jekyll](), [Homebrew](), [macOS](), [Git](), [Package Management](), [Ruby](), [Command-line interface](), [GitHub](), [Atom]() Tags: [atom](), [command-line](), [free](), [git](), [github](), [homebrew](), [how-to](), [jekyll](), [macos](), [minutes](), [personal-website](), [writing]() ### AI overview This tutorial explains how to build a free personal static website with blog capabilities using Jekyll. It covers setting up a text editor, command-line tools, Homebrew, Ruby, Jekyll, Bundler, Git, and GitHub, with examples focused on macOS. ### Source excerpt Do you want a personal website? :computer: ## Frontend Dependency Management with Browserify DevFeed: [Frontend Dependency Management with Browserify]() Original publisher: [Read original article]() Author: Wordbitly Published: 2014-10-30T20:10:27Z Content type: tutorial Language: en Sources: [Bitly]() Topics: [frontend development](), [JavaScript](), [Package Management](), [Node.js](), [npm]() Tags: [browserify](), [dependency-management](), [frontend](), [javascript](), [node-js](), [npm](), [package-management]() ### AI overview This developer article explains how Bitly adopted Browserify for frontend dependency management while overhauling its "Your Bitlinks" interface. It describes Browserify's Node.js-style module and package workflow, including bundling dependencies from an entry point into a destination file, and discusses benefits such as fewer HTTP requests and a less-polluted global namespace. ### Source excerpt With frontend development moving as fast as it does at Bitly, things can get pretty messy. We found ourselves with piles of unmanaged script tags and little indication of what was still being used in the app's current iteration. There had to be a better way! Enter Browserify! A few months ago, we embarked upon a project to totally overhaul the "Your Bitlinks" interface, and with that came the opportunity to rethink our practices and introduce frontend dependency management. Now the page looks as good behind the scenes as it does in your browser! So, what is Browserify? Browserify is a great tool that lets you write your client-side scripts like it's node, allowing you to use node's package management and module systems. Each file should be a module and explicitly require() all its dependencies. Then you simply give Browserify your main entry point, such as an overarching app file, and the name of a destination file, e.g. browserify app.js > bundle.js This example takes your network of dependencies starting at app.js and streams all the files from your network of dependencies into bundle.js. (Side note: Being familiar with the node.js environment and NPM, node's package manager, is essential for picking up Browserify. In the weeks before we started working with Browserify, I wrote and published a node module as a side project. Going through the process, making sure all the pieces were in place-- specifically the package.json-- so that I could add it into the NPM registry made figuring out Browserify much easier.) Why use Browserify? There was no question in our minds that using a frontend dependency management tool was an important step in our app's development. We considered the field of options, ultimately settling on Browserify. We didn't need the async loading functionality of Require.js and appreciated the power of using NPM, leaving Browserify as the natural choice. Leveraging node to bundle our JavaScript provides many advantages over the traditional multiplicit ## Debian Repository Manager DevFeed: [Debian Repository Manager]() Original publisher: [Read original article]() Published: 2014-05-12T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Debian](), [Tool](), [Repositories](), [Package Management](), [Ruby](), [Git](), [qemu]() Tags: [debian](), [git](), [less](), [manage](), [manager](), [qemu](), [repository](), [ruby](), [software-packages]() ### AI overview The article introduces dr, an open-source Ruby tool for setting up and managing small Debian repositories. It provides a unified interface for repository setup, package building, versioning, distribution, signing, and release management, with Git integration and support for tools such as reprepro, debhelper, debuild, and qemu. ### Source excerpt Set up and manage your own Debian repository with less effort ## Go Package Management For 2014 DevFeed: [Go Package Management For 2014]() Original publisher: [Read original article]() Published: 2014-01-16T00:00:00Z Content type: opinion Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Package Management](), [Package manager]() Tags: [ardan-labs](), [blog](), [build-tools](), [compatibility](), [developers](), [go](), [go-programming](), [golang](), [package-management](), [programming](), [versioning](), [workflows]() ### AI overview The article reviews progress toward package management for Go, including community coordination, a goals document, tool classification, user stories, test packages, and bug fixes. It argues that multiple tools may be needed and outlines compatibility, versioning, and portability guidelines for tool developers. ### Source excerpt Introduction In October 2013 I sent out a call to action to the Go community. I wanted to form a group of Gophers that would come together and help write a specification and build a working implementation of a package management tool. We are not there yet, but the group did accomplish a few things: We started a mailing list called Go package management [go-pm] where people could discuss ideas and get feedback on existing and new tools. We wrote a goals document that outlined what we wanted to accomplish along with guidelines and help for package management tool authors. We identified and categorized the existing set of tools that are available for use. We developed a set of user stories that describe the different scenarios people were facing. We started a list of packages that tool developers can use to test their tools against. We helped some of the tool developers find and fix bugs. Overall I think the last 3 months have been productive and I am pleased with the results. Building Tools I have come to appreciate that there isn't going to be a silver bullet or a one tool fits all solution. I believe a majority of the use-cases that have been defined in the goals document can be solved and building tools to handle these use-cases is worth the time and effort. If you're thinking about building a tool, please consider these guidelines which are outlined in the goals document: Work with the Go language as defined in the Go 1 spec of March 28, 2012. Don't implement solutions that require feature changes or build tools that change the way Go works. Provide backwards compatibility with go get and the convention of using VCS repositories in the import paths. The existing set of programs, build processes and workflows can't break. You must respect the existing environments and allow them to continue to function. Prevent version skewing. Don't build into the solution the potential for version skewing to occur. Such as requiring semantic versioning in the import path urls. Im ## Go Package Management Call To Action DevFeed: [Go Package Management Call To Action]() Original publisher: [Read original article]() Published: 2013-10-01T00:00:00Z Content type: opinion Language: en Sources: [William Kennedy]() Topics: [Package Management](), [Go Language](), [Tooling]() Tags: [ardan-labs](), [blog](), [community](), [go](), [go-programming](), [golang](), [package-management](), [programming](), [research](), [tooling]() ### AI overview The article calls for community participation in defining a Go package-management specification and building a working reference implementation. It proposes organizing a public working group, setting milestones, and presenting the results at GopherCon in April 2014. ### Source excerpt Nathan Youngman, with the help of others, has produced this document outlining months of research and discovery. I would appreciate everyone to honestly read it before continuing with my post. External resource on nathany.com: http://nathany.com/go-packages/ Mitchell Hashimoto also published this post on go-nuts and everyone should read this as well. External resource on groups.google.com: https://groups.google.com/forum/#!msg/golang-nuts/BMZDD6FM-QE/LX4JSs4NVLIJ These two documents outline the current capabilities and issues surrounding the Go tooling as it relates to package management. This has been discussed and discussed at length yet we still don't have a consensus on what the community will rally around. I am willing to perform all the administrative work involved in putting together a specification and working reference implementation. If we can accomplish this, then we have something that can be used by the community to build a package management tool and we all win. I have created a Google Group and I ask those of you who are interested to join. External resource on groups.google.com: https://groups.google.com/forum/#!forum/go-package-management The group is public. If you are interested in being a part of the working group please submit your request at the group. Our goal is to present our specification and working reference implementation to the community at GopherCon in April 2014. The first step will be to define a set of milestones that allow us to meet our goals by April next year. Then we need to organize the working group into teams with team leaders and members to help do the research and make recommendations. I hope some of you consider joining the group and help the community solve this problem. [Next page]()