Package Details: doomseeker 1:1.4.r0.gd47a5362-1

Git Clone URL: (read-only, click to copy)
Package Base: doomseeker
Description: A cross-platform Doom server browser
Upstream URL:
Keywords: chocolate chocolate_doom doom doomseeker odamex sonic_robo_blast_2 turok_2_remaster zandronum
Licenses: LGPL
Submitter: Pol_M
Maintainer: Pol_M
Last Packager: Pol_M
Votes: 10
Popularity: 0.000363
First Submitted: 2018-02-23 17:41 (UTC)
Last Updated: 2023-02-12 10:39 (UTC)

Dependencies (10)

Required by (7)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

Pol_M commented on 2022-08-02 20:09 (UTC)

I'll fix this during this weekend. Thanks for the report.

Technetium1 commented on 2022-08-02 19:47 (UTC) (edited on 2022-08-07 06:57 (UTC) by Technetium1)

Mising python to build in clean chroot. Might also be missing something else: build log

Pol_M commented on 2020-09-03 21:03 (UTC) (edited on 2020-09-23 07:28 (UTC) by Pol_M)

I'll try to remember this, thanks! (We'll have to consider if we want to also target aarch64, as we don't have the hardware to test this, but I'm happy that it works for you)

dleslie commented on 2020-09-02 18:31 (UTC)

This builds and runs fine on aarch64; could you add it as an architecture?

Pol_M commented on 2019-10-02 23:02 (UTC) (edited on 2019-10-07 19:53 (UTC) by Pol_M)

I accidentally deleted the last comment, sorry. Anyway, do not worry about it, tomorrow I'll do a proper consideration. But as stated, there is a reason things are as they are.

And... Things are gonna stay as they are. As repeatedly stated, things are as they are because they work this way, because doomseeker requires it's VCS to be able to compile. The best alternative I can think of would be to manually generate the necessary header file. I started a draft, but this has presented so many issues that, considering how much of a workaround it is, it is not worth the time. Also, git would still be a dependency anyway if I don't want to be uploading generated code to the AUR, which is explicitly forbidden (It would only be like header file, but I'm not taking chances ;) ). So, git is necessary at some point, and the amount of work necessary is too large to prevent building doomseeker the intended way.

sanerb commented on 2019-10-02 22:52 (UTC)

i should note that 1.3 doesn't seem to build, though- though it seems to be upstream issue:

/tmp/doomseeker/src/doomseeker/src/core/version.cpp: In static member function ‘static QString Version::changeset()’:
/tmp/doomseeker/src/doomseeker/src/core/version.cpp:30:9: error: ‘HG_REVISION_HASH_STRING’ was not declared in this scope
   30 |  return HG_REVISION_HASH_STRING;
      |         ^~~~~~~~~~~~~~~~~~~~~~~
/tmp/doomseeker/src/doomseeker/src/core/version.cpp: In static member function ‘static QString Version::revision()’:
/tmp/doomseeker/src/doomseeker/src/core/version.cpp:58:9: error: ‘HG_TIME’ was not declared in this scope; did you mean ‘LC_TIME’?
   58 |  return HG_TIME;
      |         ^~~~~~~
      |         LC_TIME
/tmp/doomseeker/src/doomseeker/src/core/version.cpp: In static member function ‘static long long unsigned int Version::revisionNumber()’:
/tmp/doomseeker/src/doomseeker/src/core/version.cpp:63:9: error: ‘HG_REVISION_NUMBER’ was not declared in this scope
   63 |  return HG_REVISION_NUMBER;
      |         ^~~~~~~~~~~~~~~~~~
make[2]: *** [src/core/CMakeFiles/doomseeker.dir/build.make:3357: src/core/CMakeFiles/doomseeker.dir/version.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:343: src/core/CMakeFiles/doomseeker.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
==> ERROR: A failure occurred in build().

Pol_M commented on 2019-10-02 22:50 (UTC)

Ok, I'll consider making the switch tomorrow, since you took the time ^-^

sanerb commented on 2019-10-02 22:46 (UTC) (edited on 2019-10-02 22:48 (UTC) by sanerb)

here's an ideal and still simple package

  • uses proper release versions with no dependency on any specific VCS version (since it uses snapshots)
  • gets rid of epoch (because you don't really need it; you can just modify pkgrel with this version)
  • all you need to do is change the pkgver variable for new releases, unless the actual build process drastically changes.

(edit: AUR comments do not like source blocks)

Pol_M commented on 2019-10-02 22:35 (UTC) (edited on 2019-10-02 22:41 (UTC) by Pol_M)

The git repository is now up and running. Bitbucket will drop in no time the Mercurial support, so indeed these days this package has needed some readjustments to keep up with the deadlines. Now, the reason for using a commit instead of the 1.3 tag is that Doomseeker is VCS dependant on compilation to determine the version and so on, and since the Mercurial code no longer worked it was necessary to change some really minor things to get it to work in git. Now, the VCS checking could have been bypassed, but that would require a manual generation of a header file, and that's more complex than what it needs to be, since I can assure you that a commit on the master branch of the official repo will not be rebased. Now, using the actual tarball is a good idea, but back when 1.1 was the official release the tarball did stop working and it was necessary to move to a more modern commit. This could be redone to go back to using the tarball, but the last thing I want is to bump the epoch every time I have to switch back and forth because Qt (for instance) now does something differently.

TLDR: I am aware of these things, it's not ideal but how it's done is the simplest and more reliable way. If things did not break, I'd do as you say.