Great featured alternative to clipman that would be great to have in MX-17 Test. Debs available on site.
https://hluk.github.io/CopyQ/
CopyQ
CopyQ
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: CopyQ
It's already in MX-15/16 repos so probably just needs to be rebuilt for stretch / MX-17.Jerry3904 wrote:Great featured alternative to clipman that would be great to have in MX-17 Test. Debs available on site.
https://hluk.github.io/CopyQ/
Code: Select all
$ apt-cache policy copyq
copyq:
Installed: (none)
Candidate: 3.0.3-1mx15+1
Version table:
3.0.3-1mx15+1 0
500 http://mxrepo.com/mx/repo/ mx15/main amd64 Packages
2.9.0-1mx150+1 0
500 http://mxrepo.com/mx/testrepo/ mx15/test amd64 Packages
Re: CopyQ
Thanks. Checked MX-17 and web search on "debian copyq" without success, but didn't think of looking back.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: CopyQ
I'll rebuild it. It should be able to go in main as it's working well in MX-16.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Re: CopyQ
I also like copyQ a lot.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: CopyQ
Yes, I've been using it since adding it to the repo. 3.0.3 is the current release.
Judging by what happened concerning the Qt5 MX apps and the added dependency for virtualbox-guest-x11, I think the Qt5 5.7 in Stretch has some direct bindings to openGL libraries that the Jessie version does not, so that's why we only see it in the MX17 builds in Vbox. Since CopyQ is also Qt5, I would guess that it also would need that override--which I hope really works, since I've only tested it with adobe-flashplugin so far. I assume we have to use it with every Qt 5 package in standard MX 17 Vbox builds---which looks like the future, since Qt 4 on the way out.
That override doesn't really do anything if the build doesn't really require it, so it's up to the maintainer if they want to slap it willy-nilly into every single rules file, but it looks more polished if we only use it where needed. Even nicer would be some code in the rules file that would detect if that package is installed and only then use that override.
Judging by what happened concerning the Qt5 MX apps and the added dependency for virtualbox-guest-x11, I think the Qt5 5.7 in Stretch has some direct bindings to openGL libraries that the Jessie version does not, so that's why we only see it in the MX17 builds in Vbox. Since CopyQ is also Qt5, I would guess that it also would need that override--which I hope really works, since I've only tested it with adobe-flashplugin so far. I assume we have to use it with every Qt 5 package in standard MX 17 Vbox builds---which looks like the future, since Qt 4 on the way out.
That override doesn't really do anything if the build doesn't really require it, so it's up to the maintainer if they want to slap it willy-nilly into every single rules file, but it looks more polished if we only use it where needed. Even nicer would be some code in the rules file that would detect if that package is installed and only then use that override.
Re: CopyQ
I pulled the latest git version from the ppa. It did not generate a virtualbox-guest-x11 dependency on either arch so I didn't have to try an override.
I do see that I need to rebuild some of the MX-17 mx-apps with an override however. I didn't notice that dependency since it was already satisfied on the antiX alpha that my VM's are based on.
I do see that I need to rebuild some of the MX-17 mx-apps with an override however. I didn't notice that dependency since it was already satisfied on the antiX alpha that my VM's are based on.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Re: CopyQ
OK...the MX apps seem to have fairly simple Qt 5 build-depends, though they pull in a lot of Qt 5 dependencies, so one of those must be to blame. Maybe we can further simplify the B-D's, possibly by trying something like what CopyQ is using and testing the MX app in a pbuilder or OBS build, and see if we can eliminate whatever is pulling in the x11 dependency. I can try that project, since I already have both of those resources available.
Hmmm..upon further thought, probably not. Dh-shlibdebs directly gets dependencies from the finished binary, so it really doesn't matter what the build-deps are, unless the build system only adds Qt 5 openGL features to the binary if the appropriate headers are available, and I'm sure that doesn't apply to the MX apps.
Hmmm..upon further thought, probably not. Dh-shlibdebs directly gets dependencies from the finished binary, so it really doesn't matter what the build-deps are, unless the build system only adds Qt 5 openGL features to the binary if the appropriate headers are available, and I'm sure that doesn't apply to the MX apps.