[aur-general] Repackaging a single binary from a package in the repos - dvisvgm from texlive-bin
Hello everyone. I recently came across a bug in dvisvgm [0] and contacted the developer about it. He was able to tell me that my issue was already fixed in the newest upstream version [1]. Currently, dvisvgm is installed as a part of extra/texlive-bin. However, TexLive (and as such the dvisvgm version that is distributed with it) only gets updated once a year [2][3], so the currently obtainable version of dvisvgm has this bug until at least April. I was wondering how I'd go about submitting a PKGBUILD that installs a single binary from texlive-bin. As far as I know, no texlive package relies on this specific version of dvisvgm (or any version of it, since it's only an auxiliary binary), so overwriting the existing version on the system shouldn't be a problem. Another issue I faced is that dvisvgm depends on texlive-bin, but also should overwrite the /usr/bin/dvisvgm that is installed through texlive-bin. How would I go about submitting this PKGBUILD? Should I submit it at all? Thanks in advance Leonard. [0] https://github.com/mgieseki/dvisvgm [1] https://github.com/mgieseki/dvisvgm/issues/150 [2] https://tug.org/texlive/#:~:text=4apr%3A%20public%20release [3] https://github.com/mgieseki/dvisvgm/issues/150#issuecomment-805955619
lennivh24--- via aur-general <aur-general@lists.archlinux.org> writes:
Hello everyone.
I recently came across a bug in dvisvgm [0] and contacted the developer about it. He was able to tell me that my issue was already fixed in the newest upstream version [1].
Currently, dvisvgm is installed as a part of extra/texlive-bin. However, TexLive (and as such the dvisvgm version that is distributed with it) only gets updated once a year [2][3], so the currently obtainable version of dvisvgm has this bug until at least April.
I was wondering how I'd go about submitting a PKGBUILD that installs a single binary from texlive-bin.
As far as I know, no texlive package relies on this specific version of dvisvgm (or any version of it, since it's only an auxiliary binary), so overwriting the existing version on the system shouldn't be a problem.
Another issue I faced is that dvisvgm depends on texlive-bin, but also should overwrite the /usr/bin/dvisvgm that is installed through texlive-bin.
How would I go about submitting this PKGBUILD? Should I submit it at all? Thanks in advance Leonard.
[0] https://github.com/mgieseki/dvisvgm [1] https://github.com/mgieseki/dvisvgm/issues/150 [2] https://tug.org/texlive/#:~:text=4apr%3A%20public%20release [3] https://github.com/mgieseki/dvisvgm/issues/150#issuecomment-805955619
Hello, TeXlive as a whole is only updated once a year, but components may get updated earlier on CTAN, and TeXlife follows CTAN. You can try if https://aur.archlinux.org/packages/tllocalmgr-git/ works for you. I only know texlive-loacalmanager, which was not working very well for me. tllocalmgr is the successor. It should create a PKGBUILD for you. You should not upload it to AUR as it will install to /usr/local, and by default files under /usr/local/bin will be preferred over such under /usr/bin. Also you can try to file a bugreport for ARCH. Also Arch Linux' texlive packages are updated now and then, not only once a year. Best Regards Stefan
participants (2)
-
lennivh24@gmail.com
-
stefan-husmann@t-online.de