Bug 23893 - pdfedit - An editor for manipulating PDF documents
Summary: pdfedit - An editor for manipulating PDF documents
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-24 23:15 CET by Kristoffer Grundström
Modified: 2018-11-25 02:18 CET (History)
2 users (show)

See Also:
Source RPM: pdfedit
CVE:
Status comment:

Attachments
Proposal spec file (2.15 KB, text/x-rpm-spec)
2018-11-24 23:16 CET, Kristoffer Grundström 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2018-11-24 23:15:42 CET 
Description of problem: I found this great, but outdated program called pdfedit and I can make it build until ./configure can't find cmake for qt3 which neither Mageia 6 or Cauldron has. It needs to be rebuilt for qt4's cmake. I set the spec file to use qt4, but it still looks for qt3.

The error shown is:

checking for QT qmake... found /usr/lib64/qt4/bin/qmake but it failed check
checking for another... found /usr/lib64/qt4/bin/qmake but it failed check
checking for another... configure: error: unable to find qmake for QT3

Can we add it?

Version-Release number of selected component (if applicable): 0.4.5
Comment 1 Kristoffer Grundström 2018-11-24 23:16:29 CET 
Created attachment 10499 [details]
Proposal spec file

CC: (none) => hamnisdude

Comment 2 David GEIGER 2018-11-25 00:34:56 CET 
This software is very old and a dead project (2010-05-11)!
Also Qt3 is dead and now Qt4 soon too!

So closed this bug as wontfix and please stop open such as bug, thanks!

CC: (none) => geiger.david68210
Resolution: (none) => WONTFIX
Status: NEW => RESOLVED

Comment 3 Kristoffer Grundström 2018-11-25 02:18:06 CET 
Is there any alternative that doesn't involve Libreoffice that can do the same job?
Note You need to log in before you can comment on or make changes to this bug.