Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Could use some feedback on a DSF packaging pull request

    Scheduled Pinned Locked Moved
    DSF Development
    4
    7
    346
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gtj0undefined
      gtj0
      last edited by

      If anyone's hacking on the DSF, I could use some feedback on a pull request that refactors the packaging stuff.

      https://github.com/chrishamm/DuetSoftwareFramework/pull/62

      I'm guessing @chrishamm is pretty busy at the moment and might not get to it for a while.

      gtjoseph opened this pull request in chrishamm/DuetSoftwareFramework

      closed Refactor packaging scripts #62

      T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @gtj0
        last edited by

        @gtj0 apologies for not sorting out a category until now, hence moving the post into here.

        I hope @chrishamm will have a chance to look at it soon. I don't have any specific comments, other than its large amount of additions/changes in one pull request which makes it more difficult to merge.

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • chrishammundefined
          chrishamm administrators
          last edited by

          This is looking great - I will check it out and merge it very soon. You could remove the dpkg-scanpackages part though, because that part has already been automated on the server side.

          Duet software engineer

          1 Reply Last reply Reply Quote 0
          • gtj0undefined
            gtj0
            last edited by

            @T3P3Tony No worries!

            @chrishamm Cool, I'll remove the scanpkgs then I'll do a separate commit/pull request for the rpm support.

            1 Reply Last reply Reply Quote 0
            • gtj0undefined
              gtj0
              last edited by

              @wilriker When you build for Arch, how are you treating the dwc "2.0.0-2" version string since the dash makes it an illegal 'Version"?

              wilrikerundefined 1 Reply Last reply Reply Quote 0
              • wilrikerundefined
                wilriker @gtj0
                last edited by wilriker

                @gtj0 Yeah, that's a special case where I rewrite the version completely to what the actual DWC version is. In the current stable package that's 2.0.0.RC8.b3. The unstable package (not published in AUR) has b4.

                EDIT: also the -2 means second repack/release of version 2.0.0so this is not really part of the version. At least for Arch Linux PKGBUILD files this will be controlled by a separate variable pkgrel.

                Manuel
                Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                with probably always latest firmware/DWC (incl. betas or self-compiled)
                My Tool Collection

                1 Reply Last reply Reply Quote 0
                • gtj0undefined
                  gtj0
                  last edited by

                  Gotcha, thanks! Yeah that's what I did with the -2. I made it part of the Release rather than Version.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA