Package Details: steamcmd latest-3

Git Clone URL: (read-only)
Package Base: steamcmd
Description: Steam Command Line Tools
Upstream URL:
Keywords: download games network server steam
Licenses: custom
Submitter: markzz
Maintainer: markzz
Last Packager: markzz
Votes: 85
Popularity: 1.667818
First Submitted: 2014-01-01 02:21
Last Updated: 2019-03-24 20:06

Pinned Comments

markzz commented on 2017-10-27 15:48

Please read the note on the Wiki before using this PKGBUILD:

Latest Comments

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

markzz commented on 2016-02-08 00:30

I disagree, so therefore I will not make it run in build().

edh commented on 2016-02-08 00:27

Partial upgrades are always unsupported! In case one starts installing upgrades without using pacman one should be aware of that pacman can not track them anymore. Furthermore pacman does not even complain about that it just assumes files to be unchanged which in this case is absolutely okay.

markzz commented on 2016-02-08 00:05

The flaw in your way is that when steamcmd updates itself, the files will then no longer be tracked by pacman in the way you want it to. The reason I did it the way in steam.install was because I didn't want to have pacman be responsible for tracking files that can change or be removed.

edh commented on 2016-02-07 23:58

My initial problem was that steamcmd was run as root in the .install file which led to /root/Steam being created. Therefore a whole dir was not being properly tracked by pacman which should not be located their anyway.
Running it in the PKGBUILD makes sure that it is not run by root (since this is prohibited) and pacman can track the created files. Furthermore the newly crafted .install file helps organize and secure game builds to come.
The error log residing under ~/.local/share/Steam/logs/stderr.txt is now just a minor problem.

markzz commented on 2016-02-07 23:47

Which doesn't solve your initial problem.

edh commented on 2016-02-07 23:38

I managed to achieve this by running " +quit" in the build() function. In addition it also lets pacman track most of the files which previously were not. Though with one minor flaw: The initial build log is still put into the users home directory.

markzz commented on 2016-02-07 23:32

Since I'm on vacation next week and am doing things in preparation for my absence, this will be put off for the moment. What my plan is to read into the steamcmd "ConVars" and to just simply change this package to save the logs and other related things into /var/lib/steamcmd/. If possible, of course.

edh commented on 2016-02-07 23:25

I got that but the location is just one variable which I set for my own personal use. It was not meant to be a copy and pasty solution.

markzz commented on 2016-02-07 23:22

I'm still putting my foot down that I'm not going to install it into /srv. Sorry.

edh commented on 2016-02-07 22:50

I would be interested whether you think something like this makes sense [1]. Please feel free to critizise whatever you want.