Writing a port for a Mono executable (Pash)

Ludwig macports at metaspasm.org
Fri Nov 13 17:14:26 PST 2015


I'm writing a port for Pash, a Power Shell clone for Mono, and am stuck as
described here: https://trac.macports.org/ticket/49656#comment:4

> Pash builds successfully via Mono’s xbuild tool, but it doesn’t have a “make
> install” equivalent, it leaves the executable in the project hierarchy at
> Source/PashConsole/bin/Debug/Pash.exe.

> Furthermore, it’s not a “normal” executable, it’s a “PE32 executable
> (console) Intel 80386 Mono/.Net assembly, for MS Windows,” meaning it has to
> be launched via Mono, e.g. mono path/to/Pash.exe.

> AFAICT none of the other ports in the mono category use xbuild, so I don’t
> have a model to follow here. I guess the right thing to do would be a
> post-install script creating a one-line launcher shell script, which is what
> would be installed in ${prefix}/bin. But I don’t know where to put the
> project directory, which is full of DLLs and stuff that the executable
> presumably depends on, and as such should be kept in its entirety.
> ${workpath} and ${portpath} are subject to being cleaned, right? What is the
> proper location for persistent files?

> Attached what I’ve got of the Portfile so far. The checksums are for the
> tarball I rolled from the source, do I attach that here or…?

> Sorry if these are dopey questions, this is my first real attempt at
> packaging a port.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 821 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20151113/60113aa0/attachment.sig>


More information about the macports-users mailing list