Package Details: atlauncher 3.4.36.3-1

Git Clone URL: https://aur.archlinux.org/atlauncher.git (read-only, click to copy)
Package Base: atlauncher
Description: A launcher for Minecraft which integrates multiple different modpacks to allow you to download and install modpacks easily and quickly.
Upstream URL: https://github.com/ATLauncher/ATLauncher
Licenses: GPL3
Conflicts: atlauncher-bin
Provides: atlauncher
Submitter: demon012
Maintainer: demon012 (RyanTheAllmighty)
Last Packager: RyanTheAllmighty
Votes: 20
Popularity: 0.84
First Submitted: 2013-09-25 21:53 (UTC)
Last Updated: 2024-04-10 07:07 (UTC)

Dependencies (3)

Required by (0)

Sources (5)

Pinned Comments

RyanTheAllmighty commented on 2021-01-30 05:18 (UTC)

Hi all.

I'm the developer of ATLauncher, and just leaving a comment to say that I'm starting to automate the updates to this package (as well as atlauncher-bin) so that they align with our official releases.

As part of this process I've made some changes which shouldn't cause any issues.

If there's any issues with this, or going forward, best to reach out in Discord (https://atl.pw/discord) or pop an issue/PR in GitHub (https://github.com/ATLauncher/ATLauncher).

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

rosspf commented on 2015-11-22 21:01 (UTC) (edited on 2015-11-22 21:01 (UTC) by rosspf)

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.

<deleted-account> commented on 2015-08-30 22:27 (UTC)

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.

<deleted-account> commented on 2015-08-30 22:14 (UTC)

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.

demon012 commented on 2015-06-14 10:16 (UTC)

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).

demon012 commented on 2015-01-19 14:03 (UTC)

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

demon012 commented on 2015-01-12 16:04 (UTC)

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.

demon012 commented on 2015-01-12 15:27 (UTC)

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.

Landrash commented on 2015-01-02 08:29 (UTC)

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

truh commented on 2014-08-18 17:02 (UTC)

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

Hot4ruh1me commented on 2014-08-17 13:59 (UTC)

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

« First ‹ Previous 1 2 3 4 Next › Last »