[Sci-freak]

Packages for MegaZeux have now been submitted to the AUR (ArchLinux User-community Repository).

2.82b
http://aur.archlinux...es.php?ID=23217

SVN (will automatically grab HEAD)
http://aur.archlinux...es.php?ID=23218

Building
1. Download the desired PKGBUILD.
2. Change directory to where the PKGBUILD is situated.
3. run "makepkg -s"
4. run "sudo pacman -U megazeux*.pkg.tar.gz"


For more information on Arch Linux, visit: http://www.archlinux.org/

Edit: the 2.82b PKGBUILD will automatically fetch the MZX source from the digitalmzx archive for each user that builds it. Is this okay for the admins? I shouldn't imagine that it'll be swamped with downloads, but if it's not acceptable then I can try to mirror it.

This post has been edited by Sci-freak: 17 January 2009 - 11:18 AM

[ajs]

Looks good to me. Thanks for doing this. You can steal a package comment from either the Debian control file or the Red Hat RPM spec in the top level.

EDIT: BTW a few small things:

• You're using GNU binutils, so --as-needed-hack might pare down duplicate linkage (like -lpthread);
  
• The flag --platform unix implicitly does --disable-updater so this could be dropped;
  
• My builds of 2.82b passed through --disable-glsl at the last minute; this renderer is incomplete and 2.82b shouldn't support it. Doesn't affect SVN;
  
• Maybe you could find a way to support a separate debug symbols package on Arch? You could use either the "debuglink" target or if the distro has a tool like Debian's dh_strip this may also work.

--ajs.

[mzxgiant]

Sci-freak, on Jan 17 2009, 05:54 AM, said:

Edit: the 2.82b PKGBUILD will automatically fetch the MZX source from the digitalmzx archive for each user that builds it. Is this okay for the admins? I shouldn't imagine that it'll be swamped with downloads, but if it's not acceptable then I can try to mirror it.

This is fine with me; just do me a favor and make sure you put "digitalmzx.net" somewhere in the process tagline when you're fetching source, if the person building it would like to know where it's coming from. Additionally, are you using the download.php-based link for that?

[Sci-freak]

ajs, on Jan 17 2009, 01:42 PM, said:

Looks good to me. Thanks for doing this. You can steal a package comment from either the Debian control file or the Red Hat RPM spec in the top level.

Thanks, I've used this as a reference, but the PKGBUILD doc asks that the description is kept to one line of text. I've managed to pare it down to the following:

"A game creation system for ANSI-esque games, featuring an interactive editor and an object-oriented scripting language."

This should hopefully cover everything important, but feel free to suggest something else.

ajs, on Jan 17 2009, 01:42 PM, said:

EDIT: BTW a few small things:

• You're using GNU binutils, so --as-needed-hack might pare down duplicate linkage (like -lpthread);
  
• The flag --platform unix implicitly does --disable-updater so this could be dropped;
  
• My builds of 2.82b passed through --disable-glsl at the last minute; this renderer is incomplete and 2.82b shouldn't support it. Doesn't affect SVN;
  
• Maybe you could find a way to support a separate debug symbols package on Arch? You could use either the "debuglink" target or if the distro has a tool like Debian's dh_strip this may also work.

--ajs.

Thanks again, but I'll have to look into the debug symbols in greater depth. Without a deal of hackery, I think the nicest way to do this would be to make a separate PKGBUILD.

mzxgiant, on Jan 17 2009, 04:33 PM, said:

This is fine with me; just do me a favor and make sure you put "digitalmzx.net" somewhere in the process tagline when you're fetching source, if the person building it would like to know where it's coming from. Additionally, are you using the download.php-based link for that?

I've included a line that echoes 'Sources fetched from http://digitalmzx.net/'. The source is fetched from http://gambit.digitalmzx.com/download.php?...d532e2eaa4ea28b


Edit: further research into ArchLinux's methodology returns that a user should recompile the package themselves for debugging symbols. Reference: http://wiki.archlinu..._Getting_Traces

This post has been edited by Sci-freak: 18 January 2009 - 02:14 PM

[Sci-freak]

Changelog

megazeux-svn 1306-2:
- Added Makefile.in.patch; binaries now install to /usr/bin rather than /usr/games
- Changed PKGBUILD to use the native way of determining the latest revision number

megazeux 2.82b-3:
- Added Makefile.in.patch; binaries now install to /usr/bin rather than /usr/games

[ajs]

I'll see if I can add a config.sh flag for the output directory in the next version. /usr/games is the correct place to put game binaries on Debian/Ubuntu, and I believe it is mentioned in the FHS specification. However I can see why it may be desirable to change this.

BTW, does Arch have a /usr/share/games directory?

--ajs.

[Sci-freak]

That decision was made primarily at a user's request and I'm still not sure if it's the best way of approaching it; however, I can see that it does simplify using the package for new users. I might consider removing the patch and including a post-install note about editing PATH. The Arch way of packaging is generally to stay away from distro-specific packages and leave everything how the developer(s) intended it.

Arch doesn't include a /usr/share/games directory, no.

[ajs]

I'm just going by the Debian guidelines, but I don't consider those to be canonical (ha ha). If you can send me a patch to make the install directory configurable from either a make variable (make BINDIR=/blah install maybe?) or ./config.sh, that'd be better than maintaining a patch to the include.

EDIT: Of course, the best solution to this would be to install a proper XDG shortcut; then it's far less important where the binary is, because the program can be launched from just about any desktop interface, like any other application.

--ajs.

[Sci-freak]

I've uploaded a patch to the megazeux sf.net project website. The patch defines two new parameters for config.sh: --bindir <dir> and --gamesdir <dir>, which change the utility binary installation path and MegaZeux binary installation path, respectively. Both parameters define absolute paths, in the style of --sysconfdir and so do not respect --prefix. Is this the desirable behaviour?

[ajs]

I added --sharedir too, and made a few other cleanups. You're credited in SVN 1315.

--ajs.