Opened 19 years ago
Closed 19 years ago
#5297 closed defect (fixed)
NEW PORT: Wordpress
Reported by: | joe@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.0 |
Keywords: | Cc: | yeled@… | |
Port: |
Description
A state-of-the-art semantic personal publishing platform
Attachments (1)
Change History (6)
Changed 19 years ago by joe@…
comment:1 Changed 19 years ago by yeled@…
I'm not sure you should be replicating the conflicting ports in a Portfile's variants.
It should bea greater problem (bug/issue)
comment:2 Changed 19 years ago by joe@…
(In reply to comment #2)
I'm not sure you should be replicating the conflicting ports in a Portfile's variants.
It should bea greater problem (bug/issue)
This is how I've handled Mediawiki, Gallery, and phpMyAdmin too... How should this be corrected for these ports?
comment:3 Changed 19 years ago by yeled@…
Cc: | yeled@… added |
---|
comment:4 Changed 19 years ago by joe@…
I guess I'm not understanding exactly what is wrong with this port. Is it something unique to this port, or an approach to variants that is part of a broader discussion? If the latter, can we perhaps commit this port for now, and agree upon a technique via the list? I'm sure I've found other ports (in addition to my own) that also use this technique of including php, apache, and mysql as variants.
comment:5 Changed 19 years ago by mww@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
commited but: -replaced depends_lib with depends_run since these are all (at most) run-time deps -I'm still very unhappy with the dependencies - though currently there is not much alternative
thanks!
Wordpress 1.5.2 Portfile