I?d like to upgrade the Drupal on Webstack to v6.4 (the latest 6.X
release, with some security fixes). Once I make sure there are no real
differences between the two versions, I?ll test it locally before
seeking to commit.
Here?s how Jyri set up Drupal 6.3 last month:
Package: drupal - this is all most ppl need
Depends on: SUNWapch22
Depends on: SUNWphp524
Depends on: SUNWphp524-mysql
Depends on: SUNWapch22-php5
Package: drupal-source - source tree
Package: drupal-demo - Jyri?s drupal_evaluation_init script
Depends on: drupal
Depends on: SUNWmysql5
6.4 could be pretty much the same (I may punch up the man pages a bit),
but some questions first:
* Because this is Webstack, the assumption is that *this* Drupal
assumes it?ll be installed and used with
Webstack?s MySQL 5, PHP 5.2.4 and Apache 2.2. Why then isn?t
SUNWmysql5 a drupal dependency?
* drupal_demo has already proven most useful for demos, etc. If,
however, someone decides not to
install/use it, the MySQL dependency isn?t resolved, and must be
installed separately. There are those who
are more comfortable installing ?manually?. An argument for
enforcing *all* Webstack/drupal dependencies?
* Devil?s advocate time: the other side of that coin is that there
could be those wishing to install
Drupal on PostgreSQL or Sun Web Server, Lighttpd, etc., some of
which are/will be in Webstack.
An argument to drop all the Webstack/drupal dependencies?
My inclination is to KISS, but it doesn?t hurt to float the ideas around
first...
Thx/ERR
--
Eric Reid
Staff Engineer, Software
Sun Microsystems, Inc.
Phone: +1 269.629.7238
Cell: +1 269.569.1042
Fax: +1 650.352.4428
Blog: http://blogs.sun.com/err
AIM: ereidsan
SL: EricReid SunMicrosystems
