Arch Linux User Repository

Replying to diff111 comment on 2023-02-17 10:06 (UTC)

Indeed, source url at PKGBUIKD no longer valid.

1 ) There is a Download javascript button at Driver. By setting printer, P2500 series, P2500, Linux, Linux Ubuntu 22.04 within the 5 drop down menus, and clicking Download, I was able to download a file from, I think, 驱动/文件下载, driver file download.

2 ) Got Pantum Linux Driver V1_1_94-1.zip. Which can be looked into with standard tools, such as bsdtar. There are licenses in several languages, 2 deb files, some shell scripts and 2 binary installers. For i386 and x86_64. The debs can also be extracted with, for example, bsdtar.

3 ) It seems to contain drivers for cups, and also sane, for several models. By looking into the binary installer with strings, they are, probably, graphical GTK binaries. Hopefully, the uninstall script reverts most, or all, the actions of the installers. And thus reveals most, or all, the actions of the binary installer.

4 ) The content of the control file of the x86_64 deb is shown below. I am confused about the Depeneds field, because I assumed there should be a GTK dependency. Perhaps GTK is only optional, which is good in my opinion. It could be the archlinux aur package title and description should be modified to better describes 驱动/文件下载, driver file download.

Package: pantum
Version: 1.1.94-1
Architecture: amd64
Section: utils
Priority: optional
Maintainer: Zhuhai Pantum Electronics Co., Ltd <support@pantum.com>
Installed-Size: 21596
Replaces: pantum-m5000-m6000-series,pantum-m6500-series-sane,pantum-m6500-series,pantum-p2000-series,pantum-p2500-series,pantum-p3000-series,pantum-cp2500dn,pantum-series,pantum-sane
Description: CUPS and SANE drivers for Pantum series printer and scanner.
 No Extended Description.
Depends: libc6 (>=2.0.0)

5 ) There seem a total of 5 Pantum related aur packages. One has to look for them by Name, Description. Searching by the Keyword Pantum yields a partial list. Some of those 5 packages are of version 1.1.99. Yet for my search above at Pantum site, I was suggested 1.1.94. I did not pursue it further. Is it reasonable of me to expect there are important differences between 1.1.94 and 1.1.99?

6 ) Since I no longer have a Pantum printer, I will request this package to be disowned.

The link http://global.pantum.com/global/wp-content/uploads/2016/01/Pantum-P2000-Series-Linux-DriverUbutun12.04V1.00-1.zip is not valid anymore, so the installation fails.

@TANWA, At 2022-06-28 13:27 (UTC)

I do not know. Am I too pessimistic assuming you will not get here a better answer? Please post here the answer, in case you will get it some where else.

can i use this for PANTUM Laser P3010DW ?

New name and description for the pantum-p2000-driver package: New name is pantum-p1000-p2000-p3000-m5100-m5200-ppd-driver. Description of the package has also been changed. Changes meant to better describe the supported printers. Both packages support the same printers, in exactly the same way. The new package has to conflicts('pantum-p2000-driver'). I intend to ask to delete the pantum-p2000-driver package.

Thank you for your work. Yes, I will take over. Give me a few days.

I no longer have a pantum printer nor the bandwidth to maintain this, would you like to take over as maintainer?

1. As of this writing, the package creates ppd files for Pantum P{10,20,30,51,52}00 models, or series. I think this should be made obvious, perhaps by using the package name or description.
2. While creating the package, makepkg interactively queries the user about files replacement. I think this is disturbing and undesired, since it is not required at all. As far as I can tell, it is due to the unzip line at the build() function. I think the absence of a prepare function makes makepkg automatically unzip the archive prior to running the build() function. Which renders the unzip line at the build() function redundant, and causes the interactive queries. I suggest to remove that line.
3. I find the comment in the build() function about the sadness of bsdtar not accurate. I think it is a quoting issue.

To summarize, I have uploaded a suggested patch to http://ix.io/2eug.