Installation Profiles and Drupal's CVS Packaging System

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
mlncn's picture
Posted by mlncn on April 10, 2008 at 9:44am

The giants of the project module and Drupal.org's CVS/packaging system (dww, hunmonk, aclight) plan to add the ability of installation profiles to have their modules packaged with them, I understand. This will be a huge step forward for their value to end users.

For more advanced users (and this is a less important consideration) I propose that this packaging be optional– that it also be possible to generate lists of modules as Drush commands or potentially other things like <href="http://drupal.org/project/dast">DAST configuration files.

Mostly I'm looking for a status report, and asking if there's an issue in the queue somewhere that I could be following and perhaps helping with. Thanks!

benjamin, Agaric Design Collective

Categories: , ,

Comments

Bump

Posted by dman on August 30, 2008 at 5:48am
dman's picture

Um yeah,
I've not seen much (any) action on this problem for a while, and am looking for the right place to track it.
Has there been any progress at all on fetching or handling of unavailable required modules?
Last time I tried it (creating a profile with unavailable dependancies on a clean distro) I got a half-broken install and warnings in unhelpful places.
Without the ability to back out and at least go fetch the requirements, custom profiles are a bit impotent. For this reason it's been hard to be enthusiastic about developing my own profiles. If this has been partially addressed recently, I apologize, but would like to know the thread(s) to follow to find out the status of this.
is a script to download needed modules the shape of things to come, or is it a dirty hack?

Dirty hack

Posted by Boris Mann on August 31, 2008 at 10:52pm
Boris Mann's picture

This won't get widespread use because so many people are on shared hosting and use FTP to install -- they need tarballs. Enabling tarball generation on Drupal.org is my personal end goal.

People today are generating tarballs on their own for ease of use, or relying on more technical users that use CVS / SVN to check out distributions.

And, of course, this is chicken and egg. If there are good profiles, then people are motivated to help get this happening. I think we'll see this happen first in language specific profiles.

I did a quick scan and didn't see the infrastructure issue post that references this, so please add one and come back and post.