What I need is the ability to do #include <emscripten.h>, and I think that is not affected by emscripten's version.

In the meantime, if you can also upgrade emscripten to its latest version, that would be fantastic ^_~

@YakoYakoYokuYoku At least to my knowledge, it also affects the JS output, so that you can directly call a function in JS on the .js output file using its original name.

Remove line breaking.

Recover comments eaten by manual line break.

Remove note from Arch and use 00755 for access permission

@xulongwu4 I was able to package it and successfully tested the sample on the GitHub README. I think it should work now, but since that might not cover everything, it would be great if you could also do some testing on your side!

I just experienced the froze @Staudey mentioned. Judging from the logs, I believe the problem is that when I try to play certain songs, it will attempt to fetch lyrics data from a wiki that has been closed, which causes it to get stuck.

1. Solidity currently has no plan to use cvc5 plus cvc5 is not even out yet, so "waiting" for it might not be a good idea.
2. As mentioned, cvc4 is an optional dependency, so it's totally fine if we don't want to include that.

Hi! I see that there are no maintainers specified for this package, so I decided to take a look myself. I was able to build it and play a few files with it. However, since I don't use this software, I'm pretty sure I'm not testing all common usages, so it would be great if you can also check it for me!

Update license

Extract extra dependencies into workdir.

Remove "networking" section since no need to manually grab dependencies.

Use the $source macro for installing additional dependencies.

Removed a duplicate dependency.

Sorry for the inconvenience! What we have in our repository is the community version. I've been trying to include the official cli, but I've been having some trouble packaging it. It's great to hear that you have a work-around!

Hi! I'm the maintainer of the protonvpn-cli package, and I personally use this piece of software, so I think I might be able to help you here. :)

In case someone wants to pick this up, I suggest doing it after vlang passes 0.3 as right now their release cycle is pretty long (the last release was in January) while breaking changes has been going on.

In T9764#186366, @sootstone wrote:

The first stable release is now available - https://github.com/ProtonVPN/linux-app/releases

From my experience, it looks like you're running out of memory. How much RAM does your computer have? Running any RAM-hungry tasks when this happens? (e.g. 20 tabs in your browser, playing Minecraft while a software is compiling, etc.)

I'm glad to give it a shot later today.

I was trying to update this revision to the latest version (0.8.6), but I messed up some git stuffs and it's taking me forever to clean & fix them. so I'll just close this and create a new one.

In D11372#189160, @ReillyBrogan wrote:

In D11372#189158, @GZGavinZhao wrote:

Note: source tarball is from PyPI, not GitHub, because they haven't released it there yet (or might not even plan to).

What's wrong with the automatically generated one (expand assets)?

Updated tarball source with the one provided by GitHub

Note: source tarball is from PyPI, not GitHub, because they haven't released it there yet (or might not even plan to).

@serebit Thanks!

Is it possible to create a new package specifically for audacity's customized version, or is that too much work?

It's ok. As long as the wofi package works, I belive both of them should be fine and are ready to submit. Thanks for helping!

@DataDrake Sorry for that!
@h3o Maybe you can try to compile the build it yourself. Follow the article about building a package and end at the part "Updating solbuild". After that, run sudo solbuild build in the directory you downloaded the package.yml file.

I've built it, but the build process is so smooth that I'm not sure if it actually works. Can you help me test it out, since I'm not sure how to test it?

Renamed package from "solc" to "solidity" to prevent confusion

In D11016#183375, @DataDrake wrote:

Actually, the package should be named solidity to match upstream.

Aha thanks! This is why I can never get a full score on my math tests.

Link to task T9709

Change:

1. Changed cmake to %cmake so that the installation files will be at /usr/bin instead of /usr/local/bin
2. Created MAINTAINERS.md and added my info
3. Rearranged dependencies' order in builddeps and changed z3 to pkgconfig(z3)
4. Removed make and cmake in builddeps

Just a note: this is related to task T9709

Haha thanks :)

I've tried to build from source and it's working. cvc4 and z3 are listed as optional dependencies (SMT solver and dependencies), so even without them we still have a stable and functional build of solidity. From my observation, they seem to be performing similar actions to make check (though I'm not sure).

May I become a maintainer?