hello
following issue #328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files,
proposing that we add support for these fields to the .info module files:
* alternatives[] - module(s) with similar functionality (alternative modules that aren't replaced/deprecated by this module. example, Admin is an alternative to Administration Menu and vice-versa)
* replaces[] - module(s) that are replaced or deprecated by this module
* replacedby[] - module(s) that replace or deprecate this module
see:
#328932-153: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
#328932-139: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
#328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files
Comments
Comment #1
joachim commentedsubscribe.
I just deprecated one of my contrib modules for a new project; replacedby[] would be very handy for this type of situation.
Comment #2
Thomas_Zahreddin commentedthe tags of pear - packages look rather complete to me:
http://pear.php.net/manual/en/guide.developers.package2.intro.php
do you think these tags are usefull?
(ok, we have no channel - or did i miss something?)
Comment #2.0
Thomas_Zahreddin commentedrelated issues
Comment #3
lpalgarvio commentedComment #18
mstrelan commentedChanging component. While system.module provides the module install form, I think extension system is more appropriate.
FWIW adding these to .info.yml files is probably not particularly discoverable, so we'd need to flesh out how this information is used.