A profile can only do harm, I think, so they should be excluded.

However, wrongly built profiles like http://drupal.org/project/b2b_store_solution do all sorts of damage. by actually including modules in themselves.

CommentFileSizeAuthor
#4 project_dependency.skip_install_profiles_and_themes_1325654_03.patch1.58 KBrfay

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I don't know how we can figure this out easily. Look for the .module or .theme or .profile? Maybe that would do it.

See #1332104: Modules, Themes, Profiles should declare their type in their .info file

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Can one simply look to see if there is [filename_same_as_info].module and therefore class as module, same for theme and profile?

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Title: Profiles need to be excluded (and why not themes?) » Profiles and themes should be excluded
Priority: Normal » Critical
rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Needs review
StatusFileSize
new project_dependency.skip_install_profiles_and_themes_1325654_03.patch1.58 KB

I believe this will do the trick. I was trying to figure out how to get it from the database, but that information is buried deeply somewhere in taxonomy. Probably not reliable to get it from there.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Needs review » Fixed

Committed: http://drupalcode.org/project/project_dependency.git/commitdiff/e6720a7

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.