On Thu, Feb 28, 2013 at 1:15 PM, Jared K. Smith <jsmith(a)fedoraproject.org>wrote:
On Wed, Feb 27, 2013 at 9:50 PM, Shawn Iwinski
> I have started packaging the development version of Drupal 8. There is
> still plenty of work to do (please help!) and I would also like to get
> maintainers of drupal6 and drupal7 packages involved.
I'm willing to help out a bit, as I maintain a half-dozen or so
drupal7 packages in Fedora.
Besides "simply" packaging Drupal itself, I am trying to
> additional features:
> * provide RPM macros -- this will help simplify spec files
> * virtual packages (i.e. "drupal8(<drupal_machine_name>)") -- this
> especially help with the requiring of sub-modules
> * virtual package auto-provides (parsed from *.info filenames) -- this
> allows a package to provide the main module itself as well as any
> sub-module(s) that are included
> * virtual package auto-requires (parsed from *.info files'
> entries) -- this will help simplify spec files
> * formalized packaging guidelines
I was thinking about this just yesterday, as it was taking me a while
to track down a bunch of sub-modules and which packages were providing
them. I think virtual provides for sub-modules is something we could
really use -- and the rest would be fantastic, if we can make it work
Automagically is what I am going for. For example, here are core's
Drupal 8 itself is still in major development and this package will
> ready for Fedora for a good while. I am doing all of my work out of
> If you would like to help out or review anything, please see the links
> Specs and issues: https://github.com/siwinski/drupal8-rpms
> Dev repos: http://repos.fedorapeople.org/repos/siwinski/drupal8/
> Draft packaging guidelines:
I added a couple of lines to the packaging guidelines around Drupal
packaging guidelines and make sure that all the new Drupal 8 packages
Thanks! Libraries were one of those things I knew we needed to look into.
guidelines. Speaking of that, I only see mention of using Apache HTTPD
specifically (if I'm looking at the correct draft). I wonder if there will
be a notion of "any" web server for packages and not tied specifically to
Apache -- for example, a package like dojo would provide the source itself
while sub-packages like dojo-httpd and dojo-nginx would provide specific
web server requires and configs. I know Remi has done this for at least
one package . I was thinking we may want to do the same type thing
for Drupal 8 for httpd and nginx.
devel mailing list