Arch Linux User Repository

The dependency xorg-server-utils needs to be replaced with xorg-apps.

@Rafmaninoff, where did you place the slash? Line 31 is a mkdir line and the package builds for me without adding a slash?

On line 31 of the pkgbuild there's a missing slash, place it back in and it builds fine.

Good catch Flaeme, updated package to add unzip to makedepends.

This package, as is, also depends on the unzip command (extra/unzip) to build which is not a part of base-devel and thus should probably be added to the makedeps.

I told you what was the problem with the package 2 months ago. I also gave you a completely functional rewritten Package and PKGBUILD in an email, which you refused to use.

Also, I am not attempting to "steal" it from you. I am only trying to get it updated and functional, because it wasn't. If someone can't simply update a package using code which was already written for them, or write their own update in the time span of 2 months, then I believe the proper thing is to step down and let someone else who is willing to maintain it do so. Heck if I was busy with things in my life and I couldn't maintain a project of mine I would gladly let someone else take over the reigns if they are willing to. I do not care one bit if I'm not the owner anymore. Nobody should as that's against the spirit of this community.

In the end, I am not interested in this petty drama. I tried multiple times to get you to do something but you kept putting me and it off. That's why I finally filed a request, due to you not being able to update the package. Anyway, guess it'll be the mods decision.

The update with the choice between shared and non shared mods directories will have to come when I have the time to finish rewriting the script but as previously stated I will not have an internet connection for 2 weeks as of tomorrow evening.

Right... I have updated the icon and bumped the version that is written in the PKGBUILD, but FYI the package is always current and always reflects the version that is current when the package is built on the users machine as it grabs the version number from inside the jar file (see the pkgver function).

rosspf, please stop trying to steal this package from me. If you genuinely have problems building this package please show me what is breaking and I can help you fix the build problem but it builds fine and runs fine on a clean install of Arch... I have tested it.

The only thing that is genuinely out of date with this package is the icon file, I am also creating a new script that uses zenity to prompt the user on first run of atlauncher whether they wish to use the shared mod directory or mod directory per user but have not had time to sort out the logic as I have been busy lately. I will be without an internet connection for 2 weeks as of tomorrow evening so if you want help it will have to be tonight or tomorrow day time.

So, by default this package has been giving me installation problems. It's related to the symlinks. Also...you really shouldn't be 777'ing a directory. Tsk tsk! ;)
I made an updated package which removes the symlink code and thus also removes the need for the synced downloads folder. Yeah there's extra space used now if two people are using the pc, but oh well.
I also updated the icon to the newer one.
If the maintainer is interested, I can send everything to him. Kinda new to helping maintain AUR4 stuff, hah.

Update: Oh, Java doesn't like Symlinked jarfiles. Carry on then. As for the Downloads symlink, I don't think it's really necessary, but I guess it could save space on a multi-user system. You should just add a conditional statement to your launch script to check if the symlink already exists before creating a new one to avoid that infinite symlink issue.

There is a problem with your launch script that 1: creates an infinite symlink in ~/.local/share/atlauncher/Downloads/Downloads/Downloads/(etc.) and 2: causes ATLauncher to throw an error that the directory it's installed in is not empty. I know that this is caused by ATLauncher's weird way of storing files (really, why can't they just use ~/.atlauncher/ like everyone else?) but I think the easiest fix would be to remove the code for symlinking the Downloads file from the launch script. Is there any specific reason you're doing that? I also think you could save some redundancy by symlinking the ATLauncher.jar instead of copying it.

Now uploaded to AUR4, also unfortunately Ryan claims that the piece of code that breaks ATLauncher's ability to use CWD for putting files in is a necessity and refuses to allow me to remove it. This is causing it so that you have to have a copy of ATLauncher in whatever directory you want the configuration files to be created.

My next plan is to refactor ATLauncher's code to use environment variables to set the location of config files, downloaded files, etc overriding the paths set by the current code (the location of the ATlauncher.jar).

For those interested, I have been working code changes to ATLauncher to enable us to be able to package it properly. The reason the current package has ATLauncher in a world writable folder in /usr is because it is currently not possible to put the jar in a separate directory to the folders it creates (e.g. instances, downloads, config, etc) because Ryan implemented a nasty Linux specific hack into the code that makes it so that instead of using the current working directory it looks for the path of the jar file and creates the folders in the same directory.

I am trying to convince him to let me remove that code and make it use the current working directory as the other operating systems do but he claims that the hack is necessary for some Linux distributions. I have tested Arch, Gentoo, Ubuntu and Debian without the code and they all worked fine.

If I am successful in getting the code removed I will update the package to use a directory within our home directories to store the config files and world instances but I will keep a single shared downloads directory (Minecraft mods are quite large). I will also at that point be able to move the jar file to the standard: /usr/share/java folder

Also for the future, if I do happen to be slacking for any reason there is a github repo for this package here: https://github.com/demon012/archlinux-package-atlauncher

If you have any improvements you want to make, fork it, make the changes and submit a pull request.

Package updated, sorry for the delay my Arch computer's SSD died and I did not have the money to replace it, just got the cash to buy a new one and rebuild it today.

Package out of date.
Atlauncher uses a new hosting provider.

Since it doesn't look like ATLauncher wants to be installed anywhere where the executing user doesn't have write permission you could modify the start script to something like this. Didn't test it, might or might not work. It's of course not a great solution but similar to what steam does.

#!/bin/sh

# fix for users of special IM modules
unset XMODIFIERS GTK_IM_MODULE QT_IM_MODULE

mkdir -p ${HOME}/.local/share
cd ${HOME}/.local/share
wget -O ATLauncher.jar -c http://www.atlauncher.com/downloads/ATLauncher.jar

exec java -jar ATLauncher.jar $@ >/dev/null

Hey demon012, your package installation directory permissions are insane. You should never give 777 in /usr/share, it's a potential security risk. Make it install in the home directory or set the /usr/share/atlauncher permissions to 744.

Regards

The launcher packaged in rev 1 was too old. It tried to query a url that does not exist anymore, resulting in a 403 error.
See: http://pastebin.com/kdCNg4gM

I've taken the liberty to update the pkgbuild. It now downloads the latest jar from the website and uses its Implementation-Version manifest attribute as the pkgver. Furthermore I changed the jar location to /usr/share/java/atlauncher/ATLauncher.jar to follow the Java packaging guidelines.
Also the License file is not needed since the CCPL is already provided under /usr/share/licenses/common/CCPL/ .
If you want to update it you can find it here: https://gist.github.com/git-commit/5846de4908482d0375f8

Why was this flagged out of date? The atlauncher updates itself within this installed package. But just incase I updated it to the latest version.