You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent conceptual changes to the repository, there is now no option for manually building the packages for Debian / Arch Linux (formerly through the package-builder script and a few support files).
There are now two ways for installing mmtex:
Through normal distro specific package manager (from OBS repositories or in the case of Arch Linux, from AUR.
By building from source and installing manually with meson to arbitrary directory (with any combination of prefix and destdir the user pleases).
OBS covers a lot of distributions and architectures, that I wasn't able to cover before, but still doesn't allow all (#4). Should there still be a way for the users to build the packages? Is it OK to require them to acquire the files from OBS and use its tooling?
The problem is that currently three distinct types of package building are supported - Arch Linux (PKGBUILD -> .pkg.zst), RPM (.spec -> .rpm) and Debian (? -> .deb). The packaging files that are now in the OBS, could theoretically be included in this repository. But the conceptual ways the packages are built for Arch + RPM vs Debian are just different.
The former requires a single file describing the build including the sources, which are downloaded.
The latter requires weird combination of two tarballs (one with the normal sources, other one adds debian subdirectory with some control files) and a special file, that extracted to a directory from which one can build the package by executing one of the many debian helper commands.
The old package-builder script just packaged a directory into a package, but this wasn't possible for .rpm packages and is not a way forward (I want the sources to be packagable in distributions normally).
@itmm If you have any needs, please comment here (provided that you still use/need mmtex).
The text was updated successfully, but these errors were encountered:
With the recent conceptual changes to the repository, there is now no option for manually building the packages for Debian / Arch Linux (formerly through the
package-builder
script and a few support files).There are now two ways for installing
mmtex
:meson
to arbitrary directory (with any combination ofprefix
anddestdir
the user pleases).OBS covers a lot of distributions and architectures, that I wasn't able to cover before, but still doesn't allow all (#4). Should there still be a way for the users to build the packages? Is it OK to require them to acquire the files from OBS and use its tooling?
The problem is that currently three distinct types of package building are supported - Arch Linux (
PKGBUILD
->.pkg.zst
), RPM (.spec
->.rpm
) and Debian (?
->.deb
). The packaging files that are now in the OBS, could theoretically be included in this repository. But the conceptual ways the packages are built for Arch + RPM vs Debian are just different.The former requires a single file describing the build including the sources, which are downloaded.
The latter requires weird combination of two tarballs (one with the normal sources, other one adds
debian
subdirectory with some control files) and a special file, that extracted to a directory from which one can build the package by executing one of the many debian helper commands.The old
package-builder
script just packaged a directory into a package, but this wasn't possible for.rpm
packages and is not a way forward (I want the sources to be packagable in distributions normally).@itmm If you have any needs, please comment here (provided that you still use/need
mmtex
).The text was updated successfully, but these errors were encountered: