Hello world, I just reviewed the update.module once more and finally committed to to CVS HEAD. Kudos to dww and Earl for their hard work. This is an important module in terms of usability, but also for the security of everything Drupal. When security releases are made available, we'll be in a much better shape. If you were to ask me, this means that Drupal is the first Open Source CMS that takes security to the next level and that is not something to take lightly. (This probably warrants a post on the drupal.org front page post but I'll leave that up to dww and/or Earl to write -- if they want.) Great job, -- Dries Buytaert :: http://www.buytaert.net/
How will the version in Drupal 6 work for people who install Drupal directly from d.o CVS? The current contrib module doesn't help at all (cvs_deploy doesn't seem to tie into it in anyway so it's not even useful to install update status). Dries Buytaert wrote:
Hello world,
I just reviewed the update.module once more and finally committed to to CVS HEAD. Kudos to dww and Earl for their hard work. This is an important module in terms of usability, but also for the security of everything Drupal. When security releases are made available, we'll be in a much better shape. If you were to ask me, this means that Drupal is the first Open Source CMS that takes security to the next level and that is not something to take lightly.
(This probably warrants a post on the drupal.org front page post but I'll leave that up to dww and/or Earl to write -- if they want.)
Great job,
-- Dries Buytaert :: http://www.buytaert.net/
-- Sean Robertson Web Developer NGP Software, Inc. seanr@ngpsoftware.com (202) 686-9330 http://www.ngpsoftware.com
On Jul 11, 2007, at 8:48 AM, Sean Robertson wrote:
How will the version in Drupal 6 work for people who install Drupal directly from d.o CVS? The current contrib module doesn't help at all (cvs_deploy doesn't seem to tie into it in anyway so it's not even useful to install update status).
a) You really must read http://drupal.org/node/124661 b) CVS deploy does interact with update(_status?) module just fine (there are both 5.x and 6.x compatible versions). The point is that dev snapshots are inherently difficult for update(_status?) to do anything with. So, if you deploy from CVS, checkout from official release tags, and then update(_status?) will work just fine. That's what (a) is about. c) If you're deploying from a branch, not an official release tag, I'd like to find a way to make cvs_deploy smart enough to somehow know the date that you last checked out, and use that as if it was the 'datestamp' entry in the project's .info file. It's comparing the datestamp in the .info file with the filedate in the available updates data that update(_status?) can tell you if a dev snapshot is out of date. I *think* I could fake it by checking the modification time on CVS/Entries: http://drupal.org/node/158526 d) People who care about the future of cvs_deploy module should help convince Dries to commit my follow-up patch to fix hook_system_info_alter() here: http://drupal.org/node/152926 Cheers, -Derek
On Jul 11, 2007, at 8:21 AM, Dries Buytaert wrote:
I just reviewed the update.module once more and finally committed to to CVS HEAD.
Yay!!! ;) Since that's now in, I'd like to introduce everyone to the "Update status advanced settings" contrib for D6 and beyond: http://drupal.org/project/update_advanced Users of update_status 5.x-2.* from contrib will notice that update.module in core lost all the fine-grained settings to ignore specific projects or even specific releases. Dries thought the UI was too complicated for core, so we moved it into contrib. However, many sites will probably want this added flexibility. So, please give it a try and file any issues you find in the issue queue: http://drupal.org/node/add/project_issue/update_advanced Also, I just added another component to the core issue queue for "update.module", so if anyone finds any problems, please report them there and I'll see them. Cheers, -Derek p.s. Eeek, should we try to rename the "update system" core component to "DB update system" or something to help avoid confusion? I've been worried about confusion between update.php and update.module for a while in the update.module issue, but no one seemed to comment or care... *shrug*
RFC on how to actions-enable the update.module: http://drupal.org/node/158541 (Consider this in the "Concept needs feedback" state) Thanks, -Derek
While we are at this, is it possible to exclude an module/theme from the update_status list? Say you have a site specific theme, which you do not want to list on the update staus list.. Is that possible at all? At the moment, my custom themes for drupal 6 are all in the state of 'No available releases found'. Stefan
Stefan Nagtegaal wrote:
While we are at this, is it possible to exclude an module/theme from the update_status list? Say you have a site specific theme, which you do not want to list on the update staus list.. Is that possible at all?
At the moment, my custom themes for drupal 6 are all in the state of 'No available releases found'.
At the moment everything is listed, but at least that's not an error condition. In general, we felt it would be better to go ahead and list/check on these. After all, if one day you suddenly turn one into a supported project on d.o, then it'll appear on your update page.
On Jul 11, 2007, at 10:32 AM, Stefan Nagtegaal wrote:
While we are at this, is it possible to exclude an module/theme from the update_status list?
Sometimes I wonder why I bother sending email to this list, since it seems no one reads what I say and I have to repeat the same information N times for the N people who wonder/ask... On Jul 11, 2007, at 9:19 AM, Derek Wright wrote:
I'd like to introduce everyone to the "Update status advanced settings" contrib for D6 and beyond:
http://drupal.org/project/update_advanced
Users of update_status 5.x-2.* from contrib will notice that update.module in core lost all the fine-grained settings to ignore specific projects or even specific releases. Dries thought the UI was too complicated for core, so we moved it into contrib. However, many sites will probably want this added flexibility.
-Derek-the-broken-record-that-always-repeats-itself
Op 12-jul-2007, om 18:48 heeft Derek Wright het volgende geschreven:
On Jul 11, 2007, at 10:32 AM, Stefan Nagtegaal wrote:
While we are at this, is it possible to exclude an module/theme from the update_status list?
Sometimes I wonder why I bother sending email to this list, since it seems no one reads what I say and I have to repeat the same information N times for the N people who wonder/ask...
On Jul 11, 2007, at 9:19 AM, Derek Wright wrote:
I'd like to introduce everyone to the "Update status advanced settings" contrib for D6 and beyond:
http://drupal.org/project/update_advanced
Users of update_status 5.x-2.* from contrib will notice that update.module in core lost all the fine-grained settings to ignore specific projects or even specific releases. Dries thought the UI was too complicated for core, so we moved it into contrib. However, many sites will probably want this added flexibility.
-Derek-the-broken-record-that-always-repeats-itself
You are right derek, my apoligize... Stefan
participants (5)
-
Derek Wright -
Dries Buytaert -
Earl Miles -
Sean Robertson -
Stefan Nagtegaal