Opened 9 years ago
Closed 6 years ago
#49137 closed enhancement (wontfix)
drupal6 6.37
| Reported by: | steenzout (Pedro Salgado) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch | Cc: | chrstphrchvz (Christopher Chavez) |
| Port: | drupal6 |
Description
- new version 6.37
- updated checksums
- added license
- updated mysql variants
- updated postgresql variants
- updated apache variants
- updated php variants
- added livecheck
Attachments (1)
Change History (10)
Changed 9 years ago by steenzout (Pedro Salgado)
| Attachment: | 20151006_drupal6_update.diff added |
|---|
comment:1 Changed 9 years ago by mf2k (Frank Schima)
| Cc: | c_dantonio@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to c_dantonio@… |
| Version: | 2.3.4 |
comment:2 Changed 9 years ago by steenzout (Pedro Salgado)
if the owner doesn't answer can you take my word for it that it works? I've used this same port to install and setup drupal on my laptop.
comment:3 Changed 9 years ago by steenzout (Pedro Salgado)
I've checked other ports and maybe we could have a single drupal portfile with all the versions (e.g. php port as something like this). if you think it's a good idea I can submit a brand new Portfile that merges drupal6 and drupal7 (and even drupal8). let me know.
comment:4 Changed 9 years ago by mf2k (Frank Schima)
Yes, a single unified drupal portfile would be good because it will be easier to manage.
comment:5 Changed 9 years ago by steenzout (Pedro Salgado)
The port maintainer isn't responding.
Could this be accepted?
Later this week I can make a port merge to a single drupal port.
comment:6 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
| Owner: | changed from c_dantonio@… to macports-tickets@… |
|---|
comment:7 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
drupal6 has been deleted: [5ce3c6b5ff/macports-ports]
comment:8 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
| Cc: | chrstphrchvz added |
|---|
comment:9 Changed 6 years ago by mf2k (Frank Schima)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Since you made white space changes along with functional changes, it is hard to tell what changes you are proposing. Ideally white space changes should be made in a separate patch. It is up to the maintainer to decide acceptance, but patches like this often never get committed because of this.