<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Chicken, Egg, or go.mod? Solving Go Circular Build-Dependencies in Debian</title>
        <link>https://peertube.debian.social/videos/watch/96607d31-d1b9-4861-92e8-5a2a33ea40f3</link>
        <description>by Andrew Lee At: DebConf26 https://debconf26.debconf.org/talks/88-chicken-egg-or-gomod-solving-go-circular-build-dependencies-in-debian/ Technical Presentation If you maintain Go related packages. You’ve seen the error: Package A needs B, but B needs A. In the Go world, this is becoming the "normal" for core libraries as Go’s modular designs for a world of "get the latest" but Debian still lives in a world of "builds in order from source". Let's see how we can clear the path easily with Go and go.mod itself to resolving the Go Circular Build-Dependencies in Debian. Room: Aula Magna - FADU Scheduled start: 2026-07-25 11:00:00-03:00</description>
        <lastBuildDate>Mon, 31 Aug 2026 09:30:07 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://peertube.debian.social</generator>
        <image>
            <title>Chicken, Egg, or go.mod? Solving Go Circular Build-Dependencies in Debian</title>
            <url>https://peertube.debian.social/client/assets/images/icons/icon-96x96.png</url>
            <link>https://peertube.debian.social/videos/watch/96607d31-d1b9-4861-92e8-5a2a33ea40f3</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://peertube.debian.social/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://peertube.debian.social/feeds/video-comments.xml?videoId=96607d31-d1b9-4861-92e8-5a2a33ea40f3" rel="self" type="application/rss+xml"/>
    </channel>
</rss>