unbuild | 📦 An unified javascript build system | Build Tool library

When you add a name to a library that means it is an private or internal library of your package. It seems that cabal currently has a bug which causes that confusing error message asking you to add SudokuSolver to your build-depends of your executable, you could instead add SudokuSolver:sud.

However, it is much more common too keep the library unnamed (or give it the same name as the package), which makes it the main public library. Then the name of the library is the same as the name of the package so you should really add SudokuSolver to the build-depends of your executable. This was the only possible option for a long time, internal libraries are relatively new. That is probably also why there are still a few issues like this.

I also notice that you can add sud as Willem van Onsem says, but only if you use cabal-version: 3.0 or earlier. With cabal-version: 3.4 you have to use the SudokuSolver:sud (package-name:internal-library-name) notation.

Edit: I have opened an issue on the cabal GitHub repo.

_git is the version, just use raspi-gpio.

It is important to distinguish between the recipe name cppzmq and the provided packages of the recipe. A single recipe can provide several packages (, -dev, -staticdev etc.).

With IMAGE_INSTALL you define which packages are included in the image.

Looking at the cppzmq recipe you can see that it only provides PACKAGES = "${PN}-dev".

Hence you should use IMAGE_INSTALL_append = " cppzmq-dev"

Since GitLab permissions are role-based, there's no way to set permissions per branch (other than setting a branch as protected in Settings / Repository / Protected Branches, which which controls who can merge not which branch can merge ). However, you could do the following:

1. In your GitLab CICD (if you don't have it set up already I highly recommend, its a handy tool) set up a check that runs always to determine which branch is trying to be merged ($CI_COMMIT_REF_NAME is what you want, see all GitLab default environment variables here) and if the branch name matches 'feature/*', then have the pipeline fail
2. Under Settings / General / Merge Requests, under Merge Checks, check the option Pipelines must succeed.

Now, if someone attempts to create a Merge Request from a feature branch, the pipeline will fail and no one will be allowed to approve the Merge Request.

you can use concurrently npm package, it allow managing your npm scripts and provides API to call npm-scripts from inside your Node app project, check programmatic-usage section.