Tags: VonC/cplx
Tags
2025-08-21 -- Python and Git on RHEL 9.6, add dev_workflow This release introduces comprehensive support for **RHEL 9.6**, adding the necessary package lists and dependencies to build tools like Python and Git on this new platform. The package management system has been significantly improved; it can now gather packages from multiple web addresses, producing a clean, sorted list of the newest available software. The installation process is more flexible, offering a new option to install single packages directly and running generic post-install steps for specific tools like `glibc` and `asciidoc`. The developer environment has been restructured by integrating a **`dev_workflow` submodule** for common setup logic, and adding numerous aliases for a smoother workflow. Build processes have also been corrected, with specific attention given to compiling Git and its documentation successfully on the new platform. Git itself comes with a Git credential helper based on GPG2 for better security. [valid]
2025-04-01 -- Glibc, GCC and flex compilations I need a more recent glibc than the one provided by the system (2.17 for RHEL 7.x), for running recent version of nodes. But, to compile glibc 2.28, I need a gcc 4.9.4. Of course, RHEL has 4.8.5, so I also need a more recent GCC and flex. This release has successfully recompiled gcc (using flex2, a more recent version of flex), and has produced wrapper scripts for all gcc-related command, so that gcc can be used by other tools (like the compilation of glibc) without setting the new gcc PATH and LD_LIBRARY_PATH: the wrapper scripts do that for you. But glibc is still not compilable. Next step: compiling make 4.x (instead of the make 3.x provided by RHEL 7.x) .env comes with install-related aliases (configure, build, install, package, deploy), and an alias to copy a tool source code (scps), complementing the existing scpe for environment setup files.
2025-03-24 -- Git cred helper and ssh wrapper Test if GCM - Git Credential Manager can be used as is (no recompilation): no. I tried: - pass (using a trusted gpg2 key, with passphrase pre-registered to the `gpg-agent`: works with pinentry-curses, provided `GPG_TTY` is set to `$(tty)`) - https://github.com/languitar/pass-git-helper, a python script, which uses a `~/.config/pass-git-helper/git-pass-mapping.ini`, but only matches `host`, not `user@host` So implement a Git credential helper using GPG2 only (not pass), and it works just fine: `src\install\env\git\bin\git-pass-helper.sh`. It will create and trust a GPG2, with passphrase, said passphrase acting as a local password. It will help encrypt a remote Git repository server token forced the SSH GIT_LOGIN identified user. (through an SSH forced command script, as described next) Add an SSH wrapper which will set: - `GIT_LOGIN` (from the `.ssh/authorized_keys` forced command parameter of `./tools/git/bin/sshwrapper.sh`) - `GIT_AUTHOR_NAME` and `GIT_AUTHOR_EMAIL` (from `./tools/git/bin/sshgitwrapper.local`) - `GIT_COMMITTER_NAME` and `GIT_COMMITTER_EMAIL` (in `./tools/git/bin/sshwrapper.sh`, after sourcing `sshgitwrapper.local`) An sshe cplxgit will work, with a local PC `~/.ssh/config` of: ``` Host cplxgit Hostname cactislux801.prod.lux.ca-indosuez.com User gitea2 IdentityFile ~/.ssh/cplxgit PreferredAuthentications publickey LogLevel ERROR #cplxgit_cd forced ``` The `#cplxgit_cd forced` will make the `sshe.bat` to open an SSH shell, and the remote SSH forced command `sshwrapper.sh` will make the appropriate `cd` + `source .env` (as well as set the GIT variables).
2025-03-19 -- Pass (password store) and GPG2 Needed for https://github.com/languitar/pass-git-helper Goal is to store HTTPS credential encrypted. Install everything to configure cplx own gpg2 keyring/secret-keyring But it still need a pinentry-tty
2025-03-18 -- Git build with meson/ninja Check out meson build system. Why meson? - https://public-inbox.org/git/ac327d98e9c287b07b8d4ab0647adbefea53ed82.1729254070.git.ps@pks.im/, - https://public-inbox.org/git/508e3783d284fd2d3bd4840907ed0bdc20bc1b23.1727881164.git.ps@pks.im/ The meson build works: ```bash ~/tools/python/bin/python -m venv venv_git ~/tools/tool/venv_git/bin$ source activate pip config -v --user set global.cert /home/path/to/certs/YourCompany.pem pip config -v --user set global.index-url https://nexus.company.com/repository/pnexus/simple/ pip config -v --user set global.trusted-host nexus.company.com/repository/pnexus/simple/ That needs Ninja: https://github.com/ninja-build/ninja/: https://github.com/ninja-build/ninja/releases/download/v1.12.1/ninja-linux.zip ~/tools/git/venv_git/bin$ unzip ninja-linux.zip pip install meson sed -i "s/python3.13_bin_bin/python3.13_bin/g" meson ./meson --version 1.7.0 ~/tools/tool/sources/2.48.1/git-2.48.1/$ meson setup --wipe -Dc_std=c99 build/ ~/tools/tool/sources/2.48.1/git-2.48.1/build$ meson configure --prefix ~/tools/git/git-2.48.1-meson options can be discovered by running `meson configure` in either a build directory or the source directory. meson compile meson install --no-rebuild meson test https://public-inbox.org/git/Z5sWCxEF3J7t8WvW@pks.im/ https://public-inbox.org/git/20241213-pks-meson-ci-v2-7-634affccc694@pks.im/ meson test -i --test-args=-vdVix -v --no-rebuild --print-errorlogs \ --maxfail 1 t0000-basic ```
2025-03-17 -- libsecret, pkgconfig pc file and pkgs reinstall * Where to store credentials? I have added the dependencies for libsecret and glib2 to work, and `~/tools/tool/sources/2.48.1/git-2.48.1/contrib/credential/libsecret$ make`: works But it does require a D-BUS session (which needs an X11 $DISPLAY and either a gnome-keyring or a KDE kwallet. So no vault backend for now. * pkgconfig pc files are correctly updated during pkg installation process. * you now can re-install all packages for a given tool: remove + install back.
PreviousNext