Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 147315 Details for
Bug 225477
Missing headers in poppler-devel?
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
IRC Log from #poppler trying to get details about issue
#poppler-2007-02-04-19h29.log (text/plain), 1.83 KB, created by
Sindre Pedersen Bjørdal
on 2007-02-04 18:33:52 UTC
(
hide
)
Description:
IRC Log from #poppler trying to get details about issue
Filename:
MIME Type:
Creator:
Sindre Pedersen Bjørdal
Created:
2007-02-04 18:33:52 UTC
Size:
1.83 KB
patch
obsolete
>--> Du snakker nå i #poppler ><Foolish> Can some of you help me in clearing this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225477 . The key question is "whether the xpdf-headers are not enabled becasue they are too new (AKA unstsable) or are deprecated so they will be removed in a later version of poppler." ><tsdgeos> xpdf headers are not installed by default because they are considered internal ><tsdgeos> and imposible to mantain binary compatibility ><Foolish> so any software depending on them to build is faulty by design? ><tsdgeos> no :D ><tsdgeos> the idea would be that they use the frontend headers ><tsdgeos> be it glib/qt/qt4 frontends ><tsdgeos> or create a plain C/C++ frontend that makes mantaining BIC easy ><Foolish> I don't understand, then again, I'm a moron. I have to convince either the maintainer of poppler to include the xpdf-headers, or the developer behind the software I'm building, referencer, not to depend on the xpdf headers to build. Which would make more sense? ><tsdgeos> Foolish: xpdf-headers are included ><tsdgeos> just not installed ><tsdgeos> you can call ./configure --installXPDFHEaders ><tsdgeos> or something if you want ><Foolish> Sure, but the package in Fedora doesn't do that as of now, IE: the headers are not available in fedora packages of poppler ><tsdgeos> right ><Foolish> So, should I convince the maintainer of said packages to inlcude the headers, or should I convince the developer of software that depends on the xpfd-headers not to do so? ><tsdgeos> what you should try to do is "abstract" the features needed by the package that is using xpdf headers and send us a patch that implements this features as a poppler frontend ><Foolish> now there's a task way over my head ><Foolish> but thanks, I'll pass the information on. OK if I log this and pass the log on to people who might know better? ><tsdgeos> yeah
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 225477
:
147141
| 147315