home.social

#dependencyresolution — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dependencyresolution, aggregated by home.social.

  1. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  2. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  3. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  4. I'm trying to understand / implement dependency resolving using the pubgrub algorithm (to use in my buildsystem nitto). But I keep running into bugs; The newset one:

    Suppose we have the following state:
    ```
    root 1.0.0 -> foo ^1.0.0, bar ^1.0.0
    foo 1.1.0 -> bar ^2.0.0
    foo 1.0.0 -> n/a
    bar 1.0.0 -> n/a
    bar 1.1.0 -> n/a
    bar 2.0.0 -> n/a
    ```

    Now after avoiding a conflict and by choosing to not select `foo 1.1.0` and deriving `not foo 1.1.0` from `{foo 1.1.0, not bar ^2.0.0}`, it derives `foo ^1.0.0` from `{root 1.0.0, not foo ^1.0.0}` even tho it is already an derivation term in the assignments! Aparentily it relates `not foo ^1.0.0` as as overlapping, and wants to add it again to the partial solution...

    #pubgrub #packagemanager #packagemanagement #dependencyresolution #programming #developing #coding #softwaredevelopment #foss #floss

  5. 🎉 GitHub Actions' new "package manager" is like watching a toddler play with Linux commands—it's cute until you realize they're in your production environment. 🤦‍♂️ Who knew dependency resolution could be more entertaining than daytime TV? 📺💥
    nesbitt.io/2025/12/06/github-a #GitHubActions #toddlerLinux #dependencyResolution #techHumor #softwareDevelopment #HackerNews #ngated

  6. 🎉 GitHub Actions' new "package manager" is like watching a toddler play with Linux commands—it's cute until you realize they're in your production environment. 🤦‍♂️ Who knew dependency resolution could be more entertaining than daytime TV? 📺💥
    nesbitt.io/2025/12/06/github-a #GitHubActions #toddlerLinux #dependencyResolution #techHumor #softwareDevelopment #HackerNews #ngated

  7. 🎉 GitHub Actions' new "package manager" is like watching a toddler play with Linux commands—it's cute until you realize they're in your production environment. 🤦‍♂️ Who knew dependency resolution could be more entertaining than daytime TV? 📺💥
    nesbitt.io/2025/12/06/github-a #GitHubActions #toddlerLinux #dependencyResolution #techHumor #softwareDevelopment #HackerNews #ngated

  8. 🎉 GitHub Actions' new "package manager" is like watching a toddler play with Linux commands—it's cute until you realize they're in your production environment. 🤦‍♂️ Who knew dependency resolution could be more entertaining than daytime TV? 📺💥
    nesbitt.io/2025/12/06/github-a #GitHubActions #toddlerLinux #dependencyResolution #techHumor #softwareDevelopment #HackerNews #ngated

  9. @f00fc7c8 I know...

    Personally, I think good that do like and / are essential to maintainable distros, even if I do violate that concept with for the sake of simplicity as .

  10. @f00fc7c8 I know...

    Personally, I think good #PackageManagers that do #DependencyResolution like #apt and #yum / #dnf are essential to maintainable distros, even if I do violate that concept with #OS1337 for the sake of simplicity as #embedded #linux #distro.

  11. @f00fc7c8 I know...

    Personally, I think good #PackageManagers that do #DependencyResolution like #apt and #yum / #dnf are essential to maintainable distros, even if I do violate that concept with #OS1337 for the sake of simplicity as #embedded #linux #distro.