see just above: post6057306

BTW inkscape 1.0 is/was quite buggy (see also before in this thread about compiling 0.92.4 with cmake)

actually the inkscape issue is a little more messy.
inkscape is not compatible with imagemagick >= 7.x so either a dedicated imagemagick-6.x installation has to be used (like archlinux does) or, since the newer 1.0 version in beta, GraphicsMagick could be used as an alternative for handling images: if neither of these two prerequisites are satisfied inkscape builds the same but without those features (and this is frankly not acceptable).
I opted for the second choice, updating inkscape to a git snapshot, hoping that the previous bug reported for 1.0b1 has been already addressed there (if not I'll update to a newer version whenever it will be available).

I haven't rebuilt my packages yet, I will do ASAP (also for the perl upgrade)...

1 members found this post helpful.

that happens because a variable has been renamed upstream (because of a typo): I applied a simple fix to it

http://cgit.ponce.cc/slackbuilds/commit/?h=efitools

regarding pandoc yes/no I personally would like to see it in current, maybe an all-in-one binary because of the many dependencies, but I also have no issues on shipping READMEs in markdown format: IMHO they are readable just fine.

FligthGear from SBo-current doesn't to likde much the new alsa packages:
--------------
/usr/bin/ld*: /usr/lib64/gcc/x86_64-slackware-linux/9.2.0/../../../../lib64/libflite_cmu_us_kal.a(cmu_us_kal.o)*: dans la fonction «*register_cmu_us_kal*»*:
cmu_us_kal.c.text+0x18d)*: référence indéfinie vers «*diphone_synth*»
/usr/bin/ld*: cmu_us_kal.c.text+0x1b4)*: référence indéfinie vers «*diphone_db_val*»
/usr/bin/ld*: /usr/lib64/gcc/x86_64-slackware-linux/9.2.0/../../../../lib64/libflite_usenglish.a(us_ffeatures.o)*: dans la fonction «*us_ff_register*»*:
us_ffeatures.c.text+0x765)*: référence indéfinie vers «*basic_ff_register*»
collect2: erreur: ld a retourné le statut de sortie 1
make[2]: *** [src/Main/CMakeFiles/fgfs.dir/build.make:7410: src/Main/fgfs] Error 1
make[1]: *** [CMakeFiles/Makefile2:1857: src/Main/CMakeFiles/fgfs.dir/all] Error 2
make: *** [Makefile:163: all] Error 2

FlightGear:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

that's strange, it seems to build fine here...

What about the LFS patch? I applied that and inkscape works as normal; I use a lot of embedded images, so what should not work as expected?
Further I noticed that maybe uniconvertor (with dependecy sk1lib) should be added to the requires; inkscape-0.92.4 likes it to be there during runtime

I think it's clarified in the patch itself: I'll paste the top here
I'll quote from the CMakeLists.txt from the latest version of inkscape in git
I think this is a matter to discuss with the maintainer...

You go wait for this ??

https://www.linuxquestions.org/quest...ml#post6057482

I understand , 5.4 Linux is not the default for now ..but in somemoment goes , and patches no affect in nothing under Linux 4.19 , i test can apply safely.

I'll wait a little because I have not been able to test it myself yet... but I will be, I think, in a couple of days.

@ponce do keep up with Your good work, it is greatly appreciated here

I hope I helped just by pointing out the issue - I repeat:

Inkscape loaded just fine with my ImageMagick-7 - i have no clue if it will work and be stable at all - but it launched just fine without any I.M-6 whatsoever on my system

Will report if any issues and will seek the IM-6 to put alongside since i rely quite a lot on Inkscape in my daily affairs.

The SBo script (on Your scripts repo) tho does try to build the 0.92.4 one - while your repo holds the 1.0-b1 built binary

FlightGear : I had to build flite to be able to build FlightGear, which doesn't appear in the queue?

I'm sure it will work fine, you'll just miss the features I pointed to above (raster extensions and image import resolution) because it won't use imagemagick at all: if you look at your build log of the inkscape package you will find in the output at the end of the configuration step, just before starting the actual build, that imagemagick support had been disabled.

- inkscape in my script repo should be at version 20191115_a4ee55b ATM, check if you have synced it correctly (instructions are linked in the first post);
- the package in my personal binary repository had been built 40 days ago, but in the meantime I had switched back to 0.92.4 then again to a newer version.

1 members found this post helpful.

AFAIK flite is an optional, autodetected, dependency of FlightGear, I don't know why it should be mandatory there: BTW, here FlightGear builds fine with or without having it installed.

Hi ponce, thanks for this explanation; I guess that without imagemagick 6-libraries plus that LFS-'patch', my built essentially has disabled imagemagick... ;-) Ah well, at least this 0.92.4 might still be more useful for me this way than the beta version (although the correction for the bug I reported last month went in last week ;-).

You mentioned GraphicsMagick as an alternative. Is it worth trying that, or does ImageMagick has to be disabled altogether?