![]() ![]() ![]() Of course if somebody is willing to step in a handle all of this, I'll be more than happy. I don't have time nor nerves for that crap. ![]() The source code dump is apparently an afterthought for the developer, and incorrect practices are used throughout the whole process.įor this reason I don't intend to go back to building from source. But the binaries must have been built from a different source in that case. It's sad to read Arch devs comments like " After many nights of plowing through code i managed to get the horror release 11.1 done".ĭ) it's clear that the source tarball is actually not used to build the binaries, because sometimes it outright fails to build because of errors and the developer sometimes corrects that afterwards. Projects should never depend on privately patched libraries (and if they do, at least bundle them), yet FFS does exactly that. Arch ones) even go as far as to patch FFS source code to not rely on the patched library functionality (again, at the expense of a different runtime behavior). That either causes the build to fail, or makes the runtime behavior of FFS different from the upstream version. ![]() There were multiple reasons why I switched from building from source to packaging pre-built binaries, including:ī) no proper build system (like cmake or meson), just a single makefile, which often required heavy patching to workĬ) the developer modifies system libraries like curl, ssh or wxwidgets, but doesn't supply their source, just an unparseable diff described in Bugs.txt in the tarball. tmp/FreeFileSync_11.6_ncOAnF/install.sh: line 75: sudo: command not found Please install "sudo" or run this installer as root. Building module freefilesync in /home/kparal/devel/flatpak//.flatpak-builder/build/freefilesync-3 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |