Package Details: devilutionx 1.2.1-1

Git Clone URL: (read-only, click to copy)
Package Base: devilutionx
Description: Diablo devolved for linux
Upstream URL:
Keywords: 1 Blizzard Diablo Game Hellfire Multiplayer Singleplayer
Licenses: custom:UNLICENSE
Submitter: robertfoster
Maintainer: robertfoster
Last Packager: robertfoster
Votes: 10
Popularity: 0.94
First Submitted: 2019-11-17 18:10
Last Updated: 2021-04-12 22:11

Latest Comments

1 2 Next › Last »

Tmk commented on 2020-11-07 13:08

Hello, I want to reevaluate my last post, for I mixed up the sources.

This time I made the following: Downloaded the source and built it like described in the instructions on the devilutionx gitpage (cd build, cmake .., make). Playing the resulting executable shows item requirements correctly.

Then I used yay to install this package. Starting this version does not show item requirements correctly.


Tmk commented on 2020-11-03 02:04

Hello, thank you for this package!

There seems to be a problem with the source tarball or with the way it gets installed. I don't know enough to judge, for me the PKGBUILD file looks fine.

I encountered a display error for item requirements, where not all requirements are shown to the user.

Upstream has another path to the source, with which item requirements are shown correctly.

The source mentioned above and the one from this package differ in shasums and creation date.


robertfoster commented on 2020-10-13 08:34

@yochananmarqos anyway I've removed the make command, replacing it with cmake. in this way you don't drive crazy for INSTALL_ROOT=$pkgdir that, as discussed in the past, it's not an install directive ("I apologize, I must've hallucinated" - your words).

For README.txt ask upstream although can be considered as "Application data". I will use vanilla resources if they don't break the build and are POSIX and Arch compliant for the majority of files placement.

yochananmarqos commented on 2020-10-11 22:19

@robertfoster: They're not my ideas, they're Arch packaging standards.

See specifically:

robertfoster commented on 2020-10-11 20:46

@yochananmarqos please ask at the upstream project. this is the official file placement provided by cmake. Anyway why README.txt is supposed to be in the wrong path? Also your assertions on pkgdir in the build function and the fact that you don't have to touch? Maybe are your ideas, but are not formalized in anyway (except for POSIX standard).

yochananmarqos commented on 2020-10-11 16:41

I updated my PKGBUILD again. The docs need to be installed manually and the README.txt ends up on the wrong place.

yochananmarqos commented on 2020-10-10 16:24

Updated PKGBUILD. Again, don't touch the $pkgdir in the build() function. It should be used only in the package() function which uses the fakeroot environment to place the files in the right places with the proper permissions.

yochananmarqos commented on 2020-03-11 21:30

@robertfoster: I apologize, I must've hallucinated the word install in there. Nevermind me, then. Good day to you.

robertfoster commented on 2020-03-11 21:27

@yochananmarqos ehi man it's a make without install INSTALL_ROOT is a global variable. sit back and relax and read what other people write. It's not

make INSTALL_ROOT=$pkgdir install


make INSTALL_ROOT=$pkgdir

is it clear now?

yochananmarqos commented on 2020-03-11 21:25

@robertfoster: See the PKGBUILD template and guidelines, make install is only ever used in the package() function. We only need make as the files are being installed manually, anyway.