[development] Version2 Module
douggreen at douggreenconsulting.com
Wed Jan 3 03:47:02 UTC 2007
I read http://drupal.org/node/94154 before starting work on this.
I was fighting the problem of knowing when I could upgrade my sites to
Drupal 5 and looking up the current DRUPAL-5 tag availability of every
contrib module for each of my sites, on an every so often basis, was
becoming time consuming.
I won't disagree that reading an html page from CVS is not the better
solution, but it works today. What I don't like about it is that I am
parsing a very specific HTML page looking for stuff inside a <select>
statement. I'd be just as happy (happier) to make an http request to a d.o
I haven't looked at project.module at all, but I think all that is missing
is to make project.module expose additional information (an RSS feed for
aggregators and some other machine readable format [XML/ini style]).
If I have the project name (i.e., views) and the module name (i.e.,
views_ui.module) can the project module return all of the releases and the
most recent cvs id's for that tag?
I'm open to other names, but may need some help getting CVS and the project
system to recognize the new name.
Under the same vain, does anyone know how to correct the project version
5.x-5.x-dev? When I created project release, I accidentally gave 5 for the
major version number instead of 1.
Bringing Ideas to Life with Software Artistry and Invention...
Providing open source software political solutions
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of Derek Wright
Sent: Tuesday, January 02, 2007 9:15 PM
To: development at drupal.org
Subject: Re: [development] Version2 Module
On Jan 2, 2007, at 5:53 PM, Earl Miles wrote:
> I really, really think using information from CVS for updates is a
> bad, bad idea and is a step backward from where we're heading.
i basically agree, but given what actually exists right now, there
aren't a lot of better alternatives. we desperately need a solution
(i.e. someone to write the code) for:
"provide module version info from drupal.org"
then, "version_updates.module" (or whatever we call this thing) can
work as contrib for older versions (5.x, 4.7.x, etc), and in D6, we
can finish implementing:
"module page could say if new releases are available"
however, until #48580 is done, all you've got to work with is screen-
scraping project nodes or something, and that's no joke.
so, while i share earl's general distaste for this particular
implementation in the long run, i can't at all blame doug for going
this route in the meantime, since you have to build code with what
exists, not with what's on my TODO list. ;) of course, i would
have rather doug knew about, wrote, tested, and provided a patch for
#48580, helped get it all the way through review, commit and d.o
deployment, and *then* built the contrib module we all wanted to see
based on that, but who can blame him for just asking cvs.drupal.org
 http://groups.drupal.org/node/1830 (among others) ;)
More information about the development