Posts

Build Package with Qi.

build-package-with-qi Build Package with Qi. Back in August 2024, I discovered a linux distro called Dragora GNU/Linux. Dragora has a unique package manager called qi . For package instalation, Qi feel like installpkg from Slackaware. For building package, qi takes some similiar approaches from PKGBUILD (Archlinux) and APKBUILD (Alpine linux). Qi uses a recipe as alternative of PKGBUILD, APKBUILD or slackbuild file to build package. Qi seems universal to use across distros, I’ve been actively using it on Ubuntu, Dragora, and LFS. Qi Recipe. Qi recipe consist of 2 parts : Package information , such as package name, description, url and package source url, etc. Build instructions , how the package will be built (extract source code, patching if needed, and install to destination directory). This is a simple qi recipe template. set -e program= version= release= description="" homepage="" license="" tarname= fetch="" ...
Post a Comment
Read more

Build gettext and libintl.so on musl.

Build-gettex-and-libintl.so-on-musl How to build gettext and libintl.so on musl. Gettext with libintl.so. After did some trials and errors I found a way to build gettext library + its libintl.so library on musl. I need the library so cosmic-files will work properly. Before I finally built gettext + libintl.so, everytime I build gettext I only get libgnuintl.so instead of libintl.so. Turns out, the solution is pretty simple. I just need to rename libintl.h header file from musl build and boom, gettext build will produce libintl.so instead of libgnuintl.so. Prepare. Musl (obviously). gettext, I use 0.24 version. Steps. Download, extract the gettext source code and change to gettext directory ! $ wget -c https://ftp.gnu.org/gnu/gettext/gettext-0.24.tar.xz $ tar -xf gettext-0.24.tar.xz $ cd gettext-0.24 Rename libintl.h header file ! $ sudo mv /usr/include/libintl.h /usr/include/libintl.h.back Build & install gettext ! $ ./configure --prefix=/usr ...
Post a Comment
Read more

How to fix "gzip: stdin: not in gzip format" error on w3m.

01.Fix-gzip-w3m How to fix “gzip: stdin: not in gzip format” error on w3m For a couple of days I faced an error when using w3m to browse some sites (e.g gist.github.com). The error seems to be related to gzip, at least that’s what I guess, because I got this error : gzip: stdin: not in gzip format Turns out, it’s not gzip’s fault. After I consulted to grok, I found some answers. Why did that happen ? Grok explain, The “gzip: stdin: not in gzip format” error when using the w3m browser to access https://gist.github.com typically indicates that w3m is receiving data it expects to be compressed in gzip format, but the data is either not compressed or in a different format. I just known that maybe w3m force gzip decompression or send an Accept-Encoding: gzip header, even when the server doesn’t provide compressed data. How to solve it ? Turns out, the solution is pretty simple. We just need to add a single line of configuration to w3m config (usually at ~/...
Post a Comment
Read more