shell-scripts | A collection of shell scripts | Script Programming library

With a bash script hook:

zsh has a number of significant differences from most Bourne-ish shells. You're running into one of the biggest differences: by default it doesn't split the result of variable expansions into separate "words". In this case, that means that the expansion of ${DOWN_MIGRATE:+--migrate-only down $NO_OF_DOWN_MIGRATIONS} is passed as a single long argument, rather than being split into three words ("--migrate-only", "down", and "2"). The single long argument confuses the script.

You can tell zsh that you want word-splitting done by adding the = modifier to the expansion:

The problem is the presence of $ in your folder name, which causes the PowerShell command to interpret it as the start of a variable reference.

The workaround is to use an aux. environment variable to store the batch file's full path and let PowerShell perform its escaping based on this variable's value:

The Start-Process call embedded in your Windows PowerShell CLI (powershell.exe) call uses positional parameter binding, for brevity:

• cmd, as the first positional argument, binds to the -FilePath parameter, i.e. the name or path of the executable to launch.

• /k, (...), as the second positional argument, binds to the -ArgumentList parameter, which accepts an array of arguments to pass the target executable, whose elements are separated with ,

Start-Process then builds a command line behind the scenes, by joining the -FilePath argument and the -ArgumentList array elements with spaces, and launches it.

As an aside:

• The way Start-Process builds the command line is actually broken, because no on-demand quoting and escaping is performed - see this answer for background information; in your specific case, however, the problem doesn't surface.

• To work around the bug it is actually preferable in general to pass a single string to -ArgumentList that contains all arguments to pass; however, in this case that would have complicated quoting (you'd need an embedded "..." string or an explicit string-concatenation expression), so the simpler solution of enumerating the arguments with , was chosen.

• See this answer for how to discover a given cmdlet's positional parameters; in short: invoke it with -? (Start-Process -?) and, in the relevant parameter set, look for the parameters whose names are enclosed in [...]; e.g.
  Start-Process [-FilePath] [[-ArgumentList] ] ...

When defining a property, it includes any line breaks into that property.

This:

Indeed, you've hit a catch-22: for the parameter declaration to work during the script-parsing phase, class [ProjectNames] must already be defined, yet you're not allowed to place the class definition before the parameter declaration.

The closest approximation of your intent using a stand-alone script file (.ps1) is to use the ValidateScript attribute instead:

${project.build.directory}/bin change this to

${project.build.directory}/appassembler/bin

Keep .sh and dll in same folder, it will work just fine. ;)

Not sure that this will work but I don't have enough reputation to comment:

• This is my my automount section in wsl.conf

First of all, I want to mention that there are two different status for failed installed packages:

• half-configured: The package is unpacked and configuration has been started, but not yet completed for some reason.
• half-installed: The installation of the package has been started, but not completed for some reason.

Source: https://www.man7.org/linux/man-pages/man1/dpkg.1.html

If you want a half-configured package, then the package must be unpackaged and it is the configuration step the one that should fail.

Now, if you follow the guide you shared with us, you may have missed the part where it says that the *.ex files are examples and are not introduced in the package so if you're modifying the file postinst.ex, these changes will no take effect.

You can remove all the *.ex files and create your own postinst file. For example I've used this one: