#31780 closed submission (fixed)
NEW: mupdf
| Reported by: | dargo@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | mupdf |
Description
please close #25675
Attachments (1)
Change History (11)
Changed 13 years ago by dargo@…
| Attachment: | mupdf.Portfile added |
|---|
comment:1 Changed 13 years ago by mf2k (Frank Schima)
| Port: | mupdf added |
|---|---|
| Version: | 2.0.3 |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|---|
| Status: | new → assigned |
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:4 Changed 13 years ago by dargo@…
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
are you sure mupdf conflicts with poppler? i did 'port content poppler' and didn't see any common files between poppler and mupdf.
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
mupdf, poppler, and xpdf-tools all want to install ${prefix}/bin/pdfinfo. I added the conflict markers after I received an activation error informing me of this conflict, so yes I'm sure.
comment:6 follow-up: 10 Changed 13 years ago by dargo@…
i've opened a bugreport on mupdf to rename the program. i'll reopen this ticket if they fix the problem.
comment:7 Changed 13 years ago by dargo@…
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
since mupdf and poppler are foremost libraries, maybe their programs should be split out to a separate tools packages like xpdf/xpdf-tools. i see in the xpdf port, the programs are renamed and the xpdf-tools symlinks to those if it's installed. this same approach would make sense for both poppler and mupdf as well. i need to have both libraries installed at the same time.
comment:8 Changed 13 years ago by skolah@…
+1 on this. I also need both installed. It's unfortunate both can't be installed at same time just because a single tool shares the same name. Renaming the tool makes sense.
comment:9 Changed 12 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
| Summary: | mupdf → NEW: mupdf |
This is a submission ticket. The port exists, so the ticket is closed. Open an enhancement ticket if you would like changes to be made to the port.
comment:10 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to dargo@…:
i've opened a bugreport on mupdf to rename the program. i'll reopen this ticket if they fix the problem.
They did fix the problem. Updating the port to 1.0 resolves the conflict. Done in r94274.
Thank you for the submission. Committed in r86461. I had to make many changes to get this to build; as you noted in comment:ticket:25675:1, you didn't test it before submitting. To test it, name the file "Portfile", "cd" to that directory in the terminal, and type "sudo port install". The directory you do this in (and those leading up to it) will need to be readable by the macports user.