Arch Linux User Repository

IMHO, given that the original repo has been inactive for 7 years, I agree that it makes sense to change the sources to a maintained fork. I would not bother renaming/creating the legacy package unless upstream resumes its activity. At the end, it's your decision as maintainer.

Also, please check the wiki on how to deal with git submodules. As it stands, you are downloading the other git repos twice when you don't update the sources URLs (once by makepkg, and then again in prepare()): https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules

I've updated the package to a working state (following a821's OOD flag message).

Any thoughts on whether or not to switch sources to fo76utils' fork of nifskope which is actively developed?

Alternatively, one could rename this package to something like nifskope-legacy-git and then create a new package with this one's current name that uses that fork.

I'd appreciate any advice from a more experienced maintainer.

This can build with this PR: https://github.com/niftools/nifskope/pull/147/commits/30954e7f01f3d779a2a1fd37d363e8a6ad560bd3

I have this in my repo since it seems like NifSkope isn't being updated atm https://github.com/katawful/nifskope

Still will not build:

==> Starting build()... g++ -c -pipe -isystem ../nifskope/lib/qhull/src -isystem ../nifskope/lib/gli/gli -isystem ../nifskope/lib/gli/external -isystem ../nifskope/lib/zlib -march=x86-64 -mtune=generic -pipe -fstack-protector-strong -fno-plt -O3 -mfpmath=sse -std=c++14 -msse2 -msse -std=gnu++1y -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_URL_CAST_FROM_STRING -DQT_DISABLE_DEPRECATED_BEFORE=0x050300 -DNIFSKOPE_VERSION=\"2.0.dev7\" -DNIFSKOPE_REVISION=\"3a85ac5\" -DLZ4_STATIC -DXXH_PRIVATE_API -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Isrc -Ilib -Ilib/fsengine -Ilib/NvTriStrip -isystem /usr/include/qt -isystem /usr/include/qt/QtOpenGL -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtXml -isystem /usr/include/qt/QtNetwork -isystem /usr/include/qt/QtCore -IGeneratedFiles/.moc -isystem /usr/include/libdrm -IGeneratedFiles/.ui -I/usr/lib/qt/mkspecs/linux-g++ -o GeneratedFiles/.obj/lightingwidget.o src/ui/widgets/lightingwidget.cpp src/ui/widgets/lightingwidget.cpp: In member function ‘void LightingWidget::setActions(QVector<QAction*>)’: src/ui/widgets/lightingwidget.cpp:72:76: error: incomplete type ‘QAction’ used in nested name specifier connect( ui->btnLighting, &QToolButton::toggled, atns.value(3), &QAction::setEnabled ); ^~~~~~~~~~ make: *** [Makefile:2679: GeneratedFiles/.obj/lightingwidget.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

Will not build:

Switched to a new branch 'makepkg' ==> Starting prepare()... ==> Starting pkgver()... fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). ==> ERROR: pkgver is not allowed to be empty. ==> ERROR: pkgver() generated an invalid version: ==> ERROR: Makepkg was unable to build nifskope-git.

If you having error about "failed to load file header (version 14020007, 20.2.0.7)" when trying to open Fallout 4 nif files, it means your XML is old. I contacted with devs and learned, that you just need to copy latest kfm.xml and nif.xml from windows binary release. Which can be found in NifSkope github. Copy them to /usr/share/nifskope and it will work. This might not be necessary in future releases though, since they noticed and said they will fix it. Currently all tools for making mods works under Arch. I use this path: Blender + GIMP > BodySlide Outfit Studio (wine) > NifSkope > Creation Kit (wine) > Fallout 4 (wine)