arch linux package

[star-buck]

Is this file the arch package:
https://github.com/TheAssassin/AppImageLauncher/releases/download/continuous/appimagelauncher-git20180419.0e72c1b.source.tar.xz

If so maybe replace .source. with.arch.

[TheAssassin]

The package is a source tarball that can be used to build packages for the application.

I am not sure what exactly you refer to with an "Arch tarball". I can't find any real docs on it (other than something on the AUR), and I have never seen any project release such tarballs on GitHub. Could you please elaborate on what needs to be packaged?

[star-buck]

Is there any arch tar.gz binary package of AIL? I thought there was one under releases, and it was that package...

…

On Apr 21, 2018 10:34, "TheAssassin" ***@***.***> wrote: The package is a source tarball that can be used to build packages for the application. I am not sure what *exactly* you refer to with an "Arch tarball". I can't find any real docs on it (other than something on the AUR), and I have never seen any project release such tarballs on GitHub. Could you please elaborate on what needs to be packaged? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#24 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAzRhhX_zqYAcbjuCrr9EItyFZzPPfGKks5tqu8VgaJpZM4Td2rl> .

[TheAssassin]

There is not, at least not yet.

CMake can generate an arbitrary tarball containing the same file layout as the other packages, just like creating a tarball of the directory created with make install DESTDIR=<out>. I can set this up within a few minutes. It's nothing Arch Linux specific, though.

@NuLogicSystems has provided a PKGBUILD file in netrunner-rolling/2018.01#56, which will be bundled in the docs directory soon, too.

[star-buck]

Yeah, it was James pkgbuild that i was thinking if and assumed there was an arch tar.gz binary package already... Arch is pretty important these days, especially with Manjaro being at the top of distrowatch and netrunner rolling based on manjaro kde, so an official tar.gz of AIL under releases would be pretty nice to have besides rpm and deb.

[TheAssassin]

So, I should try to build an Arch Linux package with that PKGBUILD file?

I'm new to Arch Linux packaging. I'll read some of the documentation, and will try to publish such packages soon.

[NuLogicSystems]

I built an arch package that is already in our netrunner repository:
http://arch.netrunner.com/netrunner/x86_64/appimagelauncher-1alpha+git20180413.08ff6b8-1-x86_64.pkg.tar.xz

[star-buck]

Can we automate this from the pkbuild like deb and rpm?

[TheAssassin]

@star-buck I think it should suffice if we add a link to these packages, then?

@NuLogicSystems how often is this package going to be updated? AppImageLauncher uses continuous deployment, i.e., packages are built for every new release.

[NuLogicSystems]

@star-buck,
I'm not sure, cmake has a way of doing this for deb and rpm built in.

[NuLogicSystems]

@TheAssassin,
I update packages when I notice updates, I'd have to monitor your github for updated releases.
If you can find a way to automate this with cpack, that would be a better solution.
I typically use manjaro tools for creating packages.
However, here is the arch documentation for packaging:
https://wiki.archlinux.org/index.php/Arch_packaging_standards
https://wiki.archlinux.org/index.php/creating_packages

[TheAssassin]

@NuLogicSystems you mean, build packages you can import? I thought you might have a platform for building packages that monitors version control systems. Similar to the openSUSE build service.

[TheAssassin]

Regarding the docs, as we have your PKGBUILD file (which seems to work fine), it's more of a "set up the environment" issue than "write the configs". I'll look into a container based solution next week.

[NuLogicSystems]

Manjaro does most of the heavy lifting when it comes to the base system, frameworks, Plasma, KDE applications, 3rd party applications, etc., and since it's a rolling distribution these are always up to date. What I package for the Netrunner repository are the extra plasmoids and applications needed that are not in the default repositories, default settings, Netrunner modifications, themes, wallpapers, etc. So far I have not needed to automate this as most of the packages only change and need updating when a new live/install ISO is needed. There are only a few select packages that need continual monitoring for upstream updates, and since I'm also a Manjaro maintainer, I can keep up with this fairly well.

[TheAssassin]

So, in order to get automatic packaging for this application, we'd have to ask Manjaro to package it upstream, right?