Problem
PDF page 8 of docs/volclava 安装及配置文档.pdf shows one install.conf with VOLC_PREFIX=/software/volclava-2.2, then offers both --type=code and --type=rpm using that same file. These installation modes interpret the prefix differently.
At current master (35fd168):
volcinstall.sh:461-463 copies VOLC_PREFIX into PREFIX.- The source install passes that destination to configure.
- The RPM install at line 299 passes it directly to
rpm -ivh --prefix.
spec/volclava.spec:27 places files under /opt/volclava-%{version}, declares Prefix: /opt, and its post-install code at line 267 derives ${RPM_INSTALL_PREFIX}/volclava-%{version}.
Consequently, the documented RPM configuration relocates the versioned directory under /software/volclava-2.2, yielding /software/volclava-2.2/volclava-2.2 for version 2.2. This differs from the /software/volclava-2.2 paths used by the following instructions. PDF page 21's separate manual RPM example correctly uses --prefix /software.
Expected result
Give distinct source and RPM configuration examples, or explicitly explain that the RPM prefix is the relocation parent directory. Keep subsequent environment/server setup paths consistent with the chosen mode.
Verification and scope
This is a documentation/source-contract check; I did not perform a privileged RPM installation. The current PDF text and installer/spec were inspected. The PDF is unchanged from the audited b361f564 version. The older #32 concerns configure/architecture directory behavior in 2.1, not this shared source/RPM example; no current open PR modifies the PDF.
Why no PR
The editable installation-manual source is not tracked. Please correct the authoritative source and regenerate the PDF; I have not patched the binary output or changed installation semantics.
Problem
PDF page 8 of
docs/volclava 安装及配置文档.pdfshows oneinstall.confwithVOLC_PREFIX=/software/volclava-2.2, then offers both--type=codeand--type=rpmusing that same file. These installation modes interpret the prefix differently.At current
master(35fd168):volcinstall.sh:461-463copiesVOLC_PREFIXintoPREFIX.rpm -ivh --prefix.spec/volclava.spec:27places files under/opt/volclava-%{version}, declaresPrefix: /opt, and its post-install code at line 267 derives${RPM_INSTALL_PREFIX}/volclava-%{version}.Consequently, the documented RPM configuration relocates the versioned directory under
/software/volclava-2.2, yielding/software/volclava-2.2/volclava-2.2for version 2.2. This differs from the/software/volclava-2.2paths used by the following instructions. PDF page 21's separate manual RPM example correctly uses--prefix /software.Expected result
Give distinct source and RPM configuration examples, or explicitly explain that the RPM prefix is the relocation parent directory. Keep subsequent environment/server setup paths consistent with the chosen mode.
Verification and scope
This is a documentation/source-contract check; I did not perform a privileged RPM installation. The current PDF text and installer/spec were inspected. The PDF is unchanged from the audited
b361f564version. The older #32 concerns configure/architecture directory behavior in 2.1, not this shared source/RPM example; no current open PR modifies the PDF.Why no PR
The editable installation-manual source is not tracked. Please correct the authoritative source and regenerate the PDF; I have not patched the binary output or changed installation semantics.