Osu: Ask for permission to package and distribute osu!lazer in Arch Linux CN repo.

[tobiichiamane]

Arch Linux CN repo is an unofficial Arch Linux repo maintained by Arch Linux CN community, containing a lot of useful/interesting packages.
I'm sincerely asking for the permission to distribute osu!lazer in the repo with package name osu-lazer.
Upstream URL will be https://osu.ppy.sh/, the package description will be The new open source version of osu!, the free-to-win rhythm game, and the license will be MIT

[beerpsi]

Isn't there already two versions of osu-lazer in the AUR?(osu-lazer, osu-lazer-git)

[farseerfc]

AUR is a place for sharing building scripts while archlinuxcn is an unofficial repo for binary packages. Using AUR (with or without AUR helper) is far less convenient than using a binary repo. A large percent of the pre-compiled packages in the archlinuxcn repo are compiled from AUR PKGBUILD.

[tobiichiamane]

@mrlacpeanut Indeed. But updating a package from AUR needs to rebuild and repackage the package, while updating from a binary repo needn't. This is basically all the reason why Arch CN repo exists.

[smoogipoo]

Once #2960 is done, we'll be distributing the AppImages ourselves. Possibly via the package repos, but undecided just yet.

[farseerfc]

Thanks a lot on the Linux packaging with AppImage formats. AppImage format does indeed have many advantages over traditional distro formats, while also some disadvantages.

Just out of curiosity, does osu upstream allow to package osu-lazer in Arch Linux official repositories? In that case the package will be tested by the Arch Linux testers and the resulted binary will be much smaller than AppImage because there is no need to bundle dependencies.

[Ferdi265]

Another thing that could be done (once the question of permission is resolved) is to use the PKGBUILD from the AUR package to build the binary package for ArchLinux CN.

Manjaro does this for a few popular and stable AUR packages like for example the "yay" AUR helper.

[peppy]

We still need someone to add build automation to generate the packages .

[Ferdi265]

about build automation: It would be as simple as some of CI/CD task that runs makepkg in a folder with the PKGBUILD.

AFAIK ArchLinux packages can be signed as well (usually with GPG keys), but I haven't looked yet into what CLI options would be needed.

makepkg is written in bash, so even if the environment the CI task runs in is not Arch-based, I think it's not hard to get it working.

I might look into that, but I don't know how much free time I'll have to do that.

[farseerfc]

2019年4月6日(土) 8:30 Ferdinand Bachmann [e-mail]:

Another thing that could be done (once the question of permission is
resolved) is to use the PKGBUILD from the AUR package to build the binary
package for ArchLinux CN.

We used to provided binary package in archlinuxcn. @peppy pointed out to us
that we cannot distribute the binary package without permission (
https://github.com/ppy/osu/issues/3723#issuecomment-439010666),
therefore we dropped the binary package from archlinuxcn (
https://github.com/archlinuxcn/repo/commit/a7920069a22ecd1635e26adf0e5eb1b5827d6fdb)
waiting for a solution.

Manjaro does this for a few popular and stable AUR packages like for
example the "yay" AUR helper.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ppy/osu/issues/3727#issuecomment-480451750, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA0lexi-9F3yQkAf-CV8fYafVbzhuQ2vks5vd9yJgaJpZM4Yfoxw
.

[farseerfc]

2019年4月6日(土) 20:24 Ferdinand Bachmann [e-mail]:

about build automation: It would be as simple as some of CI/CD task that
runs makepkg in a folder with the PKGBUILD.

AFAIK ArchLinux packages can be signed as well (usually with GPG keys),
but I haven't looked yet into what CLI options would be needed.

makepkg is written in bash, so even if the environment the CI task runs
in is not Arch-based, I think it's not hard to get it working.

I might look into that, but I don't know how much free time I'll have to
do that.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ppy/osu/issues/3727#issuecomment-480496398, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA0le2-6AKfkE-hR3oFXsEWMyOfYsUiwks5veIP1gaJpZM4Yfoxw
.

We already have a automated building solution in archlinuxcn (
https://github.com/archlinuxcn/lilac) which is fully capable of providing
nightly builds of the binary package.
This issue is about distribution permission, not about technical challenge
around building the package.

[peppy]

Please help us provide official releases by adding build support in osu-deploy or otherwise.

[ghost]

When are we getting linux support? The AUR packages are always behind updates. Is build support for linux still in works or postponed indefinitely?

[peppy]

You are welcome to PR support.

[ghost]

What? Is build support for linux still in works or postponed indefinitely?

[peppy]

It's not a primary focus since we are still focused on finishing the game.

[Joehuu]

Resolved in https://github.com/ppy/osu-deploy/pull/36.