Arch Linux User Repository

C_Schmidpeter, added you as a maintainer. I'll change PKGBUILD to mention you

@TheAirBlow: Had no chance to respond to the orphan request. I had already written an update locally. But I was still waiting for upstream to resolve the blocking issue (https://github.com/MicrosoftDocs/azure-devops-docs/issues/2966) of not having a static download link to proper releases and not just non-release commits in order to avoid relying on non-releases. Could you make me maintainer again please?

@askan The package should work again now. Could you withdraw the deletion request please?

Updated the package to the newest available build.

Sorry, didn't see the last messages somehow. I have applied @js6pak patch and now it should build again.

@js6pak: Thanks for the great patch!

Is this supposed to be working as of now? I'm getting that errored occured in Prepare() or something like that

Patch replacing node with jq and making this actually work by removing _cleanup (removed the hash comments as there is no actual hashing done?): https://gist.github.com/js6pak/a3ff27b90e2c220557726eeadf89e441

Also depends on npm and unzip. And there is an error on line 63 (_cleanup)

Undocumented dependency on pv.

@C_Schmidpeter

Using non-Arch packages for packaging Arch Linux packages is generally discouraged and should only be resorted to if there is no other alternative. (Requires special tools, is more brittle because distro packages assume distro specific stuff (which could also change) etc.)

bsdtar is enough to extract it. Also I tested it with a MonoGame Xamarin project, and it compiles successfully. It is wrong (common sense), but it works fine as it packages .deb without distro-specific stuff (script is here)

@TheAirBlow:

• This is why I chose .deb package - it already has everything that we need and we don't need to do anything with files, just copy them into ${pkgdir}

Using non-Arch packages for packaging Arch Linux packages is generally discouraged and should only be resorted to if there is no other alternative. (Requires special tools, is more brittle because distro packages assume distro specific stuff (which could also change) etc.)

@C_Schmidpeter

• It already adds symlinks properly to mono which the reverted lacks

This is why I chose .deb package - it already has everything that we need and we don't need to do anything with files, just copy them into ${pkgdir}

• Why remove the architecture libs like "usr/lib/xamarin.android/xbuild/Xamarin/Android/lib/arm64-v8a" ? They are needed for cross-compiling

Forgot about that.

• The automatic determination of the download url results in: "npm ERR! enoent ENOENT: no such file or directory, open '/ZfsRoot/temp/builddir/xamarin-android/package.json'" Needs to be added to 'sources' I assume. It is a great idea though. Once the url detection works properly, the url detection can be merged back into.

Works on my setup - AUR helper is yay. Maybe i'll do that

• The reverted code was very non-KISS/verbose/non-idiomatic in comparison (e.g. use makepkg's built-in unpacking via 'source', the 3x nested unpack can be done in one line, use makepgk's msgX functions instead of custom echo-functions etc.)

Sources cannot be dynamic, links change smh (P.S. They do not change, but using only the Build ID requires minimum changes to PKGBUILD). I didn't know that msgX functions exist, so this is good.