Angband .snap

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nekrotyrael
    Rookie
    • Jun 2009
    • 16

    Angband .snap

    Any plans to package Angband in the .snap format (http://www.snapcraft.io)?
  • Nick
    Vanilla maintainer
    • Apr 2007
    • 9647

    #2
    Short answer: What's .snap format?

    (Goes away and looks at it)

    Longer answer: Looks like a good idea. There are (as far as I'm aware) no current plans to do so, but if you (or anyone else) were volunteering, that would be great
    One for the Dark Lord on his dark throne
    In the Land of Mordor where the Shadows lie.

    Comment

    • nekrotyrael
      Rookie
      • Jun 2009
      • 16

      #3
      I took a crack at it, but since I have no experience with packaging, I've hit some major roadblocks. Namely, I managed to package angband as a snap, but not to make it work within the sandbox.

      I'll ask at the snap mailing list, hopefully they will be of help.

      Comment

      • Nick
        Vanilla maintainer
        • Apr 2007
        • 9647

        #4
        Originally posted by nekrotyrael
        I took a crack at it, but since I have no experience with packaging, I've hit some major roadblocks. Namely, I managed to package angband as a snap, but not to make it work within the sandbox.

        I'll ask at the snap mailing list, hopefully they will be of help.
        Cool, let us know if you make more progress.
        One for the Dark Lord on his dark throne
        In the Land of Mordor where the Shadows lie.

        Comment

        • nekrotyrael
          Rookie
          • Jun 2009
          • 16

          #5
          I did not get any reply from the mailing list, but I think the problem lies in the way Angband handles paths during compilation.

          As far as I can see, Angband expands the path arguments into absolute paths. That makes it not possible to have a system-wide installation with each user having their saves in $HOME, because it just gets expanded to /home/currentuser/.

          But more importantly for making a snap, the --with-no-install compile option does not make Angband run in-place, as it claims, but rather from the directory it was compiled in. So moving/renaming the Angband folder after compilation leaves it unable to start. Personally I would consider that a bug.

          The easier solution would be to make Angband compiled with --with-no-install look for its files in the directory it's being run from.

          Comment

          Working...
          😀
          😂
          🥰
          😘
          🤢
          😎
          😞
          😡
          👍
          👎