Arch Linux User Repository

It's a good suggestion but then I would simply be postponing the problem. If a new program is released in 2021, it will obviously have a different license so it will require a different package. I have already tried the 2020 version and it has a problem with HDPI resolutions. They say they know this happens with some Desktop Enviroments. Mine is KDE. I prefer to wait for a version where the problem with HDPI is completely solved. In the meantime I will have to keep seeing messages that I have pending updates knowing that it is not true. Greetings and thanks again!

@josete I recommend upgrading. the 2020 version is so much better and the upgrade is like $40, I think. They had a special going on when I bought it.

Great! It's an advance, far from being a perfect solution, but it's something. The system still indicates that there are updates when it's not true.

I humbly consider that all applications that handle licenses should split when the license refers to a different program. This is the way all other packages I have with licenses work (jriver-media-center, softmaker-office ...) I respect and admire a lot the job all mainteiners do so I just request this for a future consideration.

Greetings!

@josete Add it to your HoldPkg or IgnorePkg lists in /etc/pacman.conf.

1) I unistalled the package I had in my system. It was installed with "yay -S ..." 2) I created the package following all the steps. Everything worked perfect. 3) I installed it again using sudo pacman -U pdfstudio... I thought this way my system wouldn't tell me I have an update but it keeps saying it. Is there any way to break this "link" between the package I have installed and the AUR updates? Now, every time I run "yay -Syu" I have to answer that I don't want this update. Greetings!

Great! Thanks a lot. I'll try it.

BTW, I install AUR applications with: yay -S package_name That's why I didn't know anything about git, clone, makepkg ...

Thanks again!

@josete: There is only one step different from a manual AUR installation. You clone the repository, enter it (same so far), then checkout the revision you want to build (this step is different, the 0f0cf1f commit I looked up in "view changes" from this page as the last 2019 revision), then build and install as usual.

$ git clone https://aur.archlinux.org/pdfstudio-bin.git
$ cd pdfstudio-bin
$ git checkout 0f0cf1f
$ makepkg -i

I'm afraid I have no idea how to do anything of that.

@josete The packaging is a Git repository with full history. Just use the URL at the top of the page to clone this, then git checkout whichever commit has the version you want to build, then run makepkg. This package already has a long tail of split off AUR packages for many versions along the way and I think catering to that licensing issue is crazy. If you don't have a license and don't want to use just the free parts don't upgrade the package past the version you want to use. One you build the version you want, you can pass around the built packages to your other machines to save the trouble building the right one.

In my humble opinion there should be 2 different packages, one for version 19 and one for version 20. I have a license for PDF Studio Pro 19 but not for the new one. My system keeps saying I have 1 update available and that's not true.