![]() ![]() 3rdparty/qqbonjour/README:Mumble and Murmur build. 3rdparty/tracy/zstd/common/xxhash.h:MurmurHash 3a 2.7 GB/s 10 Austin Appleby. ![]() 3rdparty/tracy/server/tracy_xxhash.h:MurmurHash 3a 2.7 GB/s 10 Austin Appleby. 3rdparty/tracy/server/tracy_robin_hood.h: // tried lots of different hashes, let 's stick with murmurhash3. 3rdPartyLicenses/mumble-old-license-headers/LICENSE.txt: src/murmur/PBKDF2.h. 3rdPartyLicenses/mumble-old-license-headers/LICENSE.txt: src/murmur/PBKDF2.cpp. 3rdPartyLicenses/mumble-old-license-headers/LICENSE.txt:Murmur 's PBKDF2 support. $ find -type f -not -ipath "./.git/* " -not -ipath "./build/* " -exec grep -iF "murmur " /dev/null \ this limbo is not great to put it mildly.Īs is, the install target installs a dysfunctional mumble-server-user-wrapper by default and the other files would all not work with mumble-server as they require murmurd as executable. Either you as the upstream want to rename the executable (sub-project?) or not. Please put a higher priority on this issue as it is super painful to package this project this way!įiles that are not renamed and reference murmur/murmurd (there are likely more):įiles that still reference murmur/murmurd but are renamed (there are likely more):Īnd of course our general recommendation for packagers to name the server package mumble-server instead of murmur (maybe make the latter an alias for the former for backwards Why is this not done automatically using the build system in the install target though? It makes no sense for downstreams to hack around all of these issues separately. ![]() In 1.4.274 the sources are still not fully renamed, which means that I'll further stick with murmur for the Arch Linux package. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |