A Tale in the Desert

Egoista · 2013-07-17 21:31:03

Greetings, fellow Arch user. I wanted to know how to install the game "A Tale in the Desert."

I was looking at a list of games and I ran across this one in some blog. I hear that it boasts that it is one of the few non-combat MMORPGs out there. If someone could help instruct me as to how to install it, it would be greatly appreciated. I couldn't find it in the AUR and upon Googling "A Tale in the Desert Arch Linux" but did not encounter anything useful. I hope that one of you can help.

Also, if there are any other really good MMO's, please let me know. I tried installing Regnum Online but that didn't seem to work either.

Thanks in advance.

Trilby · 2013-07-17 21:34:59

What have you tried? They have a download link on their site, and a forum with topics on installation.

Egoista · 2013-07-17 22:15:52

Apologies, it was actually a bit difficult to spot out what to do.

Now, I am missing the libXpm.so.4 file and I have it in /usr/lib but not in /usr/lib32, I tried copying it there but it was the wrong ELF class (64-bit).

Where can I download a 32-bit version of libXpm.so.4?

Thank you very much for the reply.

Last edited by Egoista (2013-07-17 22:16:07)

Xabre · 2013-07-17 22:29:48

pacman -Qo /usr/lib/libXpm.so.4

See which package owns it, then see if appropriate lib32-* package exists in [multilib] repo.

edit: lib32-libxpm is in AUR: https://aur.archlinux.org/packages/lib32-libxpm/

Last edited by Xabre (2013-07-17 23:09:33)

Egoista · 2013-07-17 22:36:43

Ah, thank you very much, that seemed to have work.

Sorry to be such a burden.

Thank you all for everything.

Egoista · 2013-07-17 22:46:26

One last thing before I go, I've had this same problem with conky:

libpng warning: iCCP: known incorrect sRGB profile

And I went to thos c0debreak blog entry but that did not seem to work.

Another option I here is to downgrade libpng but am unsure as to how to do that either.

Trilby · 2013-07-17 22:56:14

That's just a warning, you don't need to do anything about it.

Xyne · 2013-07-17 23:03:32

Trilby wrote:

What have you tried? They have a download link on their site, and a forum with topics on installation.

This could easily be interpreted as encouraging someone to install a package outside of Pacman.

@Egoista
Once you have the sources and build instructions, read up on packaging and PKGBUILDs in the wiki. They are very easy to make and it will let Pacman manage the files. You can then upload it to AUR yourself for others. Installing packages outside of Pacman is strongly discouraged on Arch.

Egoista · 2013-07-17 23:09:31

Trilby wrote:

That's just a warning, you don't need to do anything about it.

Thank you, but nothing shows up when I get that error. I just get a blank window.

Xyne wrote:

Trilby wrote:
What have you tried? They have a download link on their site, and a forum with topics on installation.
This could easily be interpreted as encouraging someone to install a package outside of Pacman.
@Egoista
Once you have the sources and build instructions, read up on packaging and PKGBUILDs in the wiki. They are very easy to make and it will let Pacman manage the files. You can then upload it to AUR yourself for others. Installing packages outside of Pacman is strongly discouraged on Arch.

Thank you, Xyne, I think I've used makepkg before for installing things but with ATITD its a little different. I use packer or yaourt if I need somethin from the AUR, though.

Xyne · 2013-07-17 23:28:19

Your reply leads me to believe that there may be some confusion about makepkg/AUR/etc.

All Pacman packages are created with makepkg from PKGBUILD files. PKGBUILD files are just simple Bash scripts that set metadata (name, description, dependencies) and provide build and package functions. Those functions include the exact commands that you would run on the command line to build the package, which is why creating a PKGBUILD file is so easy.

The AUR is just a collection of PKGBUILD (and related) files. Packer, yaourt and other AUR helpers simply retrieve the PKGBUILD files and run makepkg for you (while also retrieving dependencies, which makepkg doesn't).

My suggestion was to create a PKGBUILD for ATITD so that you can build (and install) a Pacman package for it with makepkg. After that, you can contribute back to the community by uploading it to the AUR for others to use.

Again, by building a Pacman package, Pacman can track files and dependencies for the package. This avoid system clutter, problems with conflicting files, etc. It is the "right way" to do it on Arch.

Sorry if this was already clear, but I prefer to too much clarity to too little.

Trilby · 2013-07-17 23:42:31

Xyne, I would have recommended a PKGBUILD as well, except after checking the forums where the program is from it does not actually get installed. One creates a few files in the users home folder to use this, and (according to the upstream source) if it is installed outside the home directory it will not run.

Xyne · 2013-07-17 23:44:51

Trilby wrote:

Xyne, I would have recommended a PKGBUILD as well, except after checking the forums where the program is from it does not actually get installed. One creates a few files in the users home folder to use this, and (according to the upstream source) if it is installed outside the home directory it will not run.

Ah, sorry. A PKGBUILD would indeed be inappropriate in this case. I should have checked myself.

Trilby · 2013-07-17 23:48:58

No problem - those recommendations sound pretty fishy to me, which is why I just deleted the 'installer' rather than proceeding further.

I wouldn't be surprised if this could be wedged into a PKGBUILD, and made to run in a more typical manner - but that may take a good bit more effort than just going with the upstream recommendations.

Last edited by Trilby (2013-07-17 23:49:18)

Xyne · 2013-07-17 23:55:47

I still haven't looked at it, but it sounds like it would be possible to dump the files in a directory under /opt and provide a script in /usr/bin to symlink/copy them into the home directory (depending on the need to modify them).

I don't remember what it was, but I've seen at least one package that used that approach before. I think it was something that auto-updated when the user ran it, so the installed package simply provided a starting point for the per-user files.

Note: I'm not actually recommending this (or against this).

Arch Linux

#1 2013-07-17 21:31:03

A Tale in the Desert

#2 2013-07-17 21:34:59

Re: A Tale in the Desert

#3 2013-07-17 22:15:52

Re: A Tale in the Desert

#4 2013-07-17 22:29:48

Re: A Tale in the Desert

#5 2013-07-17 22:36:43

Re: A Tale in the Desert

#6 2013-07-17 22:46:26

Re: A Tale in the Desert

#7 2013-07-17 22:56:14

Re: A Tale in the Desert

#8 2013-07-17 23:03:32

Re: A Tale in the Desert

#9 2013-07-17 23:09:31

Re: A Tale in the Desert

#10 2013-07-17 23:28:19

Re: A Tale in the Desert

#11 2013-07-17 23:42:31

Re: A Tale in the Desert

#12 2013-07-17 23:44:51

Re: A Tale in the Desert

#13 2013-07-17 23:48:58

Re: A Tale in the Desert

#14 2013-07-17 23:55:47

Re: A Tale in the Desert

Board footer