Package Details: steamcmd latest-2

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: 40
Popularity: 1.522024
First Submitted: 2014-01-01 02:21
Last Updated: 2016-06-03 15:59

Dependencies (1)

Required by (4)

Sources (2)

Pinned Comments

markzz commented on 2014-01-06 00:20

steamdedicatedserver merged with steamcmd

markzz commented on 2014-01-05 23:08

This package (steamdedicatedserver) is depreciated by Valve in favor of SteamCMD.
I have recently added SteamCMD to the AUR.

Latest Comments

markzz commented on 2016-02-20 06:49

I am on vacation from the time of this comment until 2016-03-01 and will not make changes to this package until I'm back home.

02m commented on 2016-02-20 00:31

I have tried to install this, and it still creates a /root/Steam folder. Could this package be updated to not use root?

markzz commented on 2016-02-08 01:07

I'm leaving it as is for now. End of discussion.

edh commented on 2016-02-08 00:49

Just please don't run it as root in the .install file...
However like I already said it is your package! Do whatever you thing is appropiate but my point about that partial upgrades - and updating steamcmd manually is exactly that - are unsupported is not an opinion but a statement from the Arch devs.

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.

All comments