We do not have any intention of ever supporting or performing efforts to create something like the AUR for Solus. It is our belief that such unofficial repositories are to much of a legal risk for all parties and that even when done correctly, are simply too prone to breaking user systems. We've already had issues with users and OEMs providing repos and packages which break user systems or have violated license terms. You certainly are welcome to do as you wish with files used to create packages, but we do not allow advertisement of those or unofficial repositories on Solus moderated spaces.
Fri, Oct 22
We do not ship packages that do not function out of the box. That is never an acceptable solution on Solus.
Sun, Oct 17
I don't have a strong opinion, but I think protovpn or protonvpn-app would make the most sense. protonvpn-app would at least mirror linux-cli --> protonvpn-cli with linux-app --> protonvpn-app. But I also think more people will want to use the GUI instead of the CLI, so maybe protonvpn helps discoverability. I do know that not everyone understands what a GUI is, but the people who want a CLI know what that is.
Sat, Oct 16
I don't see how it isn't a name? It's a repo full of nanorc files. Arch is the only distro that currently ships these using that name and I don't agree with their decision.
Sorry, I gave them more credit than I should have and didn't read through the script to see what it was doing. My point still stands that having both get imported is problematic.
The name of this package should be nanorc to match the upstream repo.
Those aren't the same thing. With the current state of this patch both sets of syntax are always fully read in and parsed. The nanorc language doesn't assume that files are separate entities, they are more like scripts which get executed in order of inclusion. If you have two different files containing a syntax with the same name, the one read second takes precedent, but nano will have already read the previous syntax definition into memory. With --lite the files don't get installed at all in scopatz which means that only one syntax is read in instead of two.
Fri, Oct 15
Wonder if it might be worth playing with that --lite flag they have in scopatz. In my mind it makes sense to use the upstream nanorc if available and then supplement with scopatz. The main thing I was hoping to see us fix was vendoring scopatz in our own package sources.
Going to need more to go on here. Afaict this is yet-another-chromium browser, so it would really need to show some compelling value add.
Going to move this to Needs More Info until we can get more information from hplip.
Only accepting this on the condition that it has/is given a sane configuration out of the box.
I think at the moment, I'm a bigger fan of relying on pyenv since it keeps everything self-contained. I'd like to see more of a discussion on the advantages of Solus-built interpreters to normal development processes before making a decision.
I'd like to see 2.9.1 released before we accept this.
Tentatively accepting, but this needs Clojure to build since...it's written in clojure.
Looks like we need an update to 1.9 for sof-firmware which is @TClark77 's package.
Apologies. That was a separate issue.
I believe I saw that @kyrios123 was looking into this. Assigning since he is the MATE maintainer.
We already have too many out-of-tree drivers. At least the ones we have support lots of devices. I'd rather not add new ones that only work for a singular piece of hardware.
We don't allow beta software into the repo and this hasn't seen any updates in 5+ years. Marking as DOA. And again, do not change edit and visibility policies.
Tellico was removed from the repo due to a lack of a maintainer. And once again, do not change the visibility and edit policies.
Pinging @Girtablulu since he maintains the KDE packages. It looks like this hasn't seen an update in a year, which leads me to believe there might be issues with KF5 updates breaking it, but I'd like a second opinion.
@bjk Please don't change visibility and edit policies.
Wed, Oct 13
We are committed to providing an accessible environment for our users. The last thing we want for Budgie is take away from the experience that we have cultivated there. So rest-assured, these things are certainly on our radar.
Fri, Oct 8
Tue, Sep 28
Have I mentioned lately that I hate autotools?
Sat, Sep 25
Please don't reopen Tasks. Given that it was over a year between the last Beta and this first stable release, we need to see that this will get frequent enough updates to warrant inclusion. Doubly so because of its dependence on GTK3 and ICU which often have world-breaking updates.
Sep 2 2021
Aug 31 2021
@h3o Only the first one would even merit a package request, but it's MIT and actively maintained, so have at it.
Aug 27 2021
Fixed by R2789:40aeeb4c452d: Update to 3.1.0
Aug 25 2021
Aug 17 2021
Jul 26 2021
No. All of the issues with GNOME Pie that led to its removal are still there. The maintainer has more or less deprecated the project and a single release after 3 years of inactivity doesn't negate that. Doubly so when they have made it clear that you should be using their newer project:
Jul 24 2021
@ReillyBrogan Please don't pester maintainers for updates. Most of the ARM Cortex ecosystem is still on GCC 7 or 8 support (MBED especially). There's no rush to update these.
Jul 10 2021
Jul 5 2021
After installation user needs to be added to input group using sudo usermod -a -G input $USER for controller to work. Can it be done during the installation?
AFAIK the only way to add the user to the correct group is with a custom usysconf trigger.
Jun 20 2021
Jun 17 2021
Jun 16 2021
Jun 15 2021
Jun 14 2021
Jun 11 2021
While I see the appeal, there's a couple of reasons I don't think we should add this:
What are you trying to use this for?
Jun 10 2021
Is it possible to create a new package specifically for audacity's customized version, or is that too much work?
Jun 9 2021
Jun 5 2021
I'm really hesitant to accept this since it has only had two patch releases since I rejected it 2 years ago. Is TeXStudio not enough? I ask as someone who made the switch from one to the other because Texmaker was quite buggy at the time.