Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: Review Request: drupal-views - Provides a method for site designers to control content presentation
https://bugzilla.redhat.com/show_bug.cgi?id=359911
------- Additional Comments From limb@jcomserv.net 2008-02-13 14:53 EST ------- (In reply to comment #9)
Actually, no. I was originally going to take over the Yakuake package, but was beaten to it. I'm actually thinking of packaging up some Drupal modules and themes myself now, thats why I 'reviewed' this.
I see. Practice makes perfect. :)
I thought of an odd issue though, to do with Drupal Module versioning schemes: Say a module is currently 5.x-2.0, it would be packaged as 2.0, yes, but when that module is ported to core 6.0 it would now be 6.x-1.0, necessitating an epoch bump if we wish to call it version 1.0? Is that the intention?
Well, not necessarily. As this is the first drupal module in Fedora, this would be the place to decide that. The versioning as I have it now strips ouit the drupal core version and leaves just the module version. I handle the drupal core requirement in the Requires.
My assumption going forward is that there will only be one major version of drupal in each Fedora release, so that I should probably put a 'less than' clause in the Requires. The catch is that this would mean that I'd really need to coordinate the updating of drupal core with all the modules. I suppose I could look at perl and it's modules as a model for how to handle that.
Not being a heavy drupal customizer myself, I'm curious how quickly after a major version release modules get updated.