7 Oct 2024

Previous: 30 Sep 2024 Next: 14 Oct 2024

  1. Mon

    1. package management paper

      1. X cite go rox blog post

      2. DOING add citations for all package managers

      3. X syntax -> bundle format

      4. X vesion formula

      5. X src vs bin -> binary caching in features column

      6. X repo release in description; ecosystem and name together

      7. DOING add order of magnitude packages (and order by)

      8. X packaging language

        cabal - https://cabal.readthedocs.io/en/stable/cabal-package-description-file.html#package-descriptions packaging language - dsl or edsl (with power of host language) DSL/eDSL

      9. X add sandboxing field

      10. X add subsections links to section 2

      11. X add dune

      12. X add B/P/C to toolchain field

      13. X concurrent versions - be clear about solving

      14. X Resolution hypergraph annd Resolved graph

      15. X tigher footnotes

      16. X binary bundles and provisioning, reorder figure 1 before table to talk about provisioning

      17. X section 4: onramp - language and bundle; formalisation; offramp

      18. ~ section 6: use to provide rust packages https://doc.rust-lang.org/cargo/commands/cargo-vendor.html

      19. X solving instead of resolving?

        Exponentials sound sciency Reify

  2. Tue

    1. package management paper

      1. X inline figures

      2. ~ debian supports OR version formula

  3. Wed

    1. package management paper

  4. Thur

    1. package management paper

      1. typos

      2. X opam dependency formula variables

      3. X provision network requests

      4. ~ thinking about it, I actually think the opam file format is more of a packaging language and less of a bundle

      5. CANCELED replace deployment section with related work

      6. X 5.1 then go home

  5. Fri

    1. package management paper

      1. I’m thinking about whether we really need to define ecosystems as a bigraph; we don’t use the motion part of bigraphs

        1. Unless… we can express resolving as a BRS?

      2. issues:

        1. we want to track the resolved graph, not just the resolved set of packages, so that we know which package satisfies a dependency if multiple show up in the graph

          e.g. if we have deps(a)={{b, c}} but the SAT encoding to solve the edges is probably inefficient

        2. boolean logic representation in the hypergraph and SAT encoding is probably inefficient

          how does the zeroinstall solver do it?

        3. a first-class feature resolution encoding – and could this subsume optional dependencies

          how could we represent this in SAT?

      3. patrick: it’s meant to show how we unifiy all of these things NOT BE FAST

        and be simple in it’s use of mathmatical objects Features are just an exponentuial blowup of the versions rust can install. E.g. the unificaition is the exposion.

      4. exloring the feature space and pulling out the commonalities

      5. not build a real system

  6. Sat

    1. package management paper

      1. diagramming et all

  7. Sun

    1. package management paper

      1. X feedback on 4.1

      2. X boolean diagram

      3. Nix service deployment

      4. Basically, Nix is a great deployment model but suffers from a bad language and non-FSH.

        what if we had a cross-ecosystem way of describing dependencies and then different backends for deployment on different systems

      5. X fill in sandboxing

      6. X patrick simplify the conflicts to be conflict sets

      7. X capitalize figure

      8. X section 5

      9. X cargo features optional deps

      10. CANCELLED cargo features can we have multiple feature sets?

      11. CANCELLED 4.2.1 version ordering zeroinstall SAT and cost function opium/cudf

        idea around more efficient SAT solving

      12. X conflict set clarification

      13. CANCELLED diagram full page

      14. X opam-giga-repository numbres

      15. X fix figure 1 - waiting for patrick

      16. X conclusion (kinda)

      17. X data availability statement

      18. CANCELLED re-read section 4.3.2

      19. X abstract

      20. ~ table 1 with numbers and citations

      21. ~ proof read

      22. future thoughts: cost functions, SAT performance, providing packages, ecosystem translations, hyper-specialised package managers