# Package Management Published articles for Package Management. 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. ## 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... ## Using a Package Manager in GitHub Actions DevFeed: [Using a Package Manager in GitHub Actions]() Original publisher: [Read original article]() Author: Sidrah Abdullah Published: 2025-08-31T19:08:15Z Content type: tutorial Language: en Sources: [Baeldung - Ops]() Topics: [ci](), [CI/CD](), [C++]() Tags: [apt](), [ci](), [deployment-tools](), [deployment-tools-git-docker-container-github-actions-package-management-ubuntu](), [docker-container](), [git](), [github-actions](), [package-management](), [tutorial](), [ubuntu](), [workflow]() ### AI overview A tutorial on installing packages with apt-get in GitHub Actions workflows, including why clean Ubuntu runners need setup, a basic lcov example, and potential permission errors. ### Source excerpt Learn how to safely and wisely use a package manager within GitHub Actions. Related Stories Get Files Modified in a PR in GitHub Actions Use Private Docker Image in GitHub Actions Using GitHub Actions to Create .env File in the Workflow ## 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 ## 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. ## 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 ## Taylor's Morning Routine & Laravel's Open Source Pledge DevFeed: [Taylor's Morning Routine & Laravel's Open Source Pledge]() Original publisher: [Read original article]() Author: Hank Published: 2024-10-08T01:30:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Pull Request](), [modern web development]() Tags: [github](), [laravel](), [open-source](), [package-management](), [php](), [pull-requests](), [vue-js]() ### AI overview Laravel describes its Open Source Pledge, including $34,000 in contributions to foundational projects such as the PHP Foundation, Composer, and Vue.js. The article also outlines a daily pull-request review routine across Laravel's open-source ecosystem. ### Source excerpt I start every morning by opening up a GitHub search that shows me [all the open pull requests](https://github.com/search?q=org%3Alaravel+is%3Apr+is%3Aopen) across Laravel's open source ecosystem. It's... ## How to upgrade Alpine Linux 3.19 to 3.20 DevFeed: [How to upgrade Alpine Linux 3.19 to 3.20]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-24T11:25:52Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [Linux](), [upgrade](), [Server](), [Docker]() Tags: [alpine-linux](), [how-to](), [incus](), [intermediate](), [linux](), [package-management](), [server](), [upgrade]() ### AI overview A tutorial explains how to upgrade Alpine Linux installations from version 3.19 to 3.20, including backups, repository changes, package updates, and rebooting. It also covers LXD container snapshots and lists selected Alpine 3.20 software and system changes. ### Source excerpt I am using Alpine Linux v3.18 or v3.19 with my LXD/Incus server. How do I upgrade Alpine Linux v3.19 to Alpine Linux v3.20? How can I upgrade Alpine Linux v3.18 to Alpine Linux v3.20? Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to upgrade Alpine Linux 3.19 to 3.20 appeared first on nixCraft. ## 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-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. ## 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 ## 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 ## 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. ## Package Management conflicts Continuous Delivery DevFeed: [Package Management conflicts Continuous Delivery]() Original publisher: [Read original article]() Author: mick Published: 2013-06-26T20:42:28Z Content type: article Language: en Sources: [Finn.no]() Topics: [Package Management](), [CI/CD](), [Continuous Deployment (CD)](), [API](), [Code]() Tags: [api-design](), [continuous-delivery](), [continuous-deployment](), [dependencies](), [package-management](), [transitive-dependencies]() ### AI overview The article examines tensions between package management and Continuous Delivery. It explains that package releases cannot be undone once downloaded, whereas deployment changes can be rolled back, while API design and modularity limit how far Continuous Delivery can be applied. It proposes emphasizing safety and API design lower in the stack and delivery speed higher in the stack. ### Source excerpt The idea of package management is to correctly operate and bundle together various components in any system. The practice of package management is a consequence from the design and evolution of each component's API. Package management is tedious but necessary. It can also help to address the 'fear of change'. We can minimise package management by minimising API. But we can't minimise API if we don't have experience with where it comes from. You can't define for yourself what the API of your code is. It is well beyond that of your public method signatures. Anything that with change can break a consumer is API. Continuous Delivery isn't void of API despite fixed and minimised interfaces between runtime services, each runtime service also contains an API in how it behaves. The big difference though is you own the release change, a la the deployment event, and if things don't go well you can roll back. Releasing artifacts in the context of package management can not be undone. Once you have released the artifact you must presume someone has already downloaded it and you can't get it back. The best you can do it release a new version and hope everyone upgrades to it quickly. Push code out from behind the shackles of package management take advantage of continuous delivery! Bearing in mind a healthy modular systems design comes from making sure you got the api design right - so the amount one can utilise CD is ultimately limited, unless you want to throw out modularity. In general we let components low in the stack "be safe" by focusing on api design over delivery time, and the opposite for components high in the stack. High in the stack doesn't refer to front-end code Code at the top of the stack is that free of package management and completely free for continuous deployment. Components with direct consumers no longer sit at the top of the stack. As components consumers multiple, and they become transitive dependencies, they move further down the stack. Typically entrop ## el-get 1.1, with 174 recipes DevFeed: [el-get 1.1, with 174 recipes]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-12-20T15:45:00Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [Package Management](), [pacman](), [apt]() Tags: [apt](), [emacs](), [hooks](), [package-management](), [packages](), [pacman](), [release]() ### AI overview This release announces el-get 1.1 with 174 recipes. It adds support for pacman, Mercurial, Subversion, and darcs; improves apt-get prompt handling; changes synchronous installation behavior; automatically removes previous failed installations; and overhauls the build facility. ### Source excerpt Yes, you read it well, el-get currently features 174 recipes, and is now reaching the 1.1 release. The reason for this release is mainly that I have two big chunks of code to review and the current code has been very stable for awhile. It seems better to do a release with the stable code that exists now before to shake it this much. If you're wondering when to jump in the water and switch to using el-get, now is a pretty good time.