Skip to main content ↑ ↓
Topic: Package request: libratbag  (Read 831 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Package request: libratbag

Since for some reason libratbag depends on soystemd's logind (but can be compiled to use elogind), it would be nice if the patched version were available in the Artix repos.
Thanks

Re: Package request: libratbag

Reply #1 –
I have a libratbag-nosystemd-git which was removed from the AUR because it is not compatible with Arch Linux (depends on stuff that conflicts with systemd).

Here is it's PKGBUILD.

So maybe someone wants to build on it.

Re: Package request: libratbag

Reply #2 –
You should've created a libratbag-maybesystemd package that has
Code: [Select]
arch-meson -Dsystemd=true "${OPTS[@]}" || arch-meson -Dsystemd=false -Dlogind_provider=elogind "${OPTS[@]}"
:P.

(Not that it would work, I see the same user went on a spree removing all sorts of nosystemd/noudev packages, even ones that do compile and work on a stock Arch install. Finally, systemd-policed).

Quote
Since for some reason libratbag depends on soystemd's logind

"For some reason" = "a NIH version of sudoers using JavaScript and logind".

Re: Package request: libratbag

Reply #3 –
Quote from: capezotte – on
You should've created a libratbag-maybesystemd package that has
Code: [Select]
arch-meson -Dsystemd=true "${OPTS[@]}" || arch-meson -Dsystemd=false -Dlogind_provider=elogind "${OPTS[@]}"
Well, in that case I would not first try to build and fail, but do a check with `pacman` which packages are installed, and depending on this set `depends` array and build options and `provides`. And maybe `$pkgdesc` ;-).

It could then just be `libratbag-git`, but that already exists.

This really could be a clean solution.

Quote from: capezotte – on
a NIH version of sudoers
What does "NIH" mean?

Regards!

Re: Package request: libratbag

Reply #4 –
Generally, how do we get non-systemd packages added into Artix? I have libratbag-nosystemd-git installed now, but also see that it was removed due to MarsSeed's rampage against any package that does not use systemd.

Re: Package request: libratbag

Reply #5 –
Quote from: dreieck – on
Quote from: capezotte – on
You should've created a libratbag-maybesystemd package that has
Code: [Select]
arch-meson -Dsystemd=true "${OPTS[@]}" || arch-meson -Dsystemd=false -Dlogind_provider=elogind "${OPTS[@]}"
Well, in that case I would not first try to build and fail, but do a check with `pacman` which packages are installed, and depending on this set `depends` array and build options and `provides`. And maybe `$pkgdesc` ;-).

It could then just be `libratbag-git`, but that already exists.

This really could be a clean solution.

As I said, even packages that technically work on a stock Arch install were removed (meaning even a compromise can still trigger the mods), and since libratbag is packaged in the official Arch repositories, this isn't a solution for the stable release.

Quote
Quote from: capezotte – on
a NIH version of sudoers
What does "NIH" mean?

"Not invented here". More specifically something that reinvents the wheel in a needlessly complex way, for something that could be had by only slightly tweaking existing tools.

Polkit has hooks for GUI password prompts¹ and scriptable configuration over sudo, which is why desktop-oriented tools are attracted to it, but only a few users will care about (or even notice) the lock-in.

¹Nowadays sudo has those, but Polkit is so entrenched people often forget the existence of this feature, and the typical Linux DE's already use it everywhere.

Re: Package request: libratbag

Reply #6 –
Quote from: jahway603 – on
it was removed due to MarsSeed's rampage against any package that does not use systemd
There's a proper word befitting such folks, but my comme-il-faut upbringing prohibits me from uttering it.

Quote from: dreieck – on
Here is it's PKGBUILD.
Saved for convenience because I know someone will be irritated.

Re: Package request: libratbag

Reply #7 –
Quote from: nous – on
Quote from: dreieck – on
Here is it's PKGBUILD.
Saved for convenience
I think you should change
Code: [Select]
# Maintainer:  dreieck
to
Code: [Select]
# Maintainer:  nous
# Contributor: dreieck
since you seem in charge for maintaining the fork at gitea.artixlinux.org/nous.
Quote from: nous – on
because I know someone will be irritated.
Who and how? MarsSeed? What power does anyone have over pastebin? Or what do you mean with "because I know someone will be irritated."?

Regards!

Re: Package request: libratbag

Reply #8 –
Off-Topic: "won" fights; other nosystemd-packages not in the AUR.

---

Quote from: capezotte – on
As I said, even packages that technically work on a stock Arch install were removed (meaning even a compromise can still trigger the mods),
I also did "win" a fight with MarsSeed, about kate-root.

---

If anyone is interested (to mirror?), I also have other -nosystemd packages:


Regards!

Re: Package request: libratbag

Reply #11 –
Quote from: nous – on
Just use a friendlier source host. Our pastebin service is another alternative.

I don't know if this would fit Artix's pocket, but hosting an instance of aurweb (or a Rust rewrite of it :P) would be interesting.

Pastebin risks getting lost to the sands of time (and it's annoying to download software that includes patches, like miraclecast in the above example), and scattering users across GitHub/Lab/ea/Codeberg hurts discoverability.

Quote from: dreieck – on
Do you have a command line tool for it?

See the end of https://paste.artixlinux.org/api (though it's never worked for me, all I ever got in the stdout was "Invalid API Key".

Re: Package request: libratbag

Reply #12 –
Quote from: capezotte – on
Quote from: dreieck – on
Do you have a command line tool for it?

See the end of https://paste.artixlinux.org/api (though it's never worked for me, all I ever got in the stdout was "Invalid API Key".
I currently do not want to code a script for it.

If you want to save the files I have provided, just do it yourself from the URLs I have provided.

The paste service I use keeps them for 7 days, then deletes them.

I have them on my harddisk and can provide again on request (ideally as one single archive).

Regards!