From a package controller, there are 2 approaches:
1. There is a method 'override core by package' (I forget the exact name, but searching the forums and howtos on that will get you to it).
2. Copy a file into the root override during package install (which can also be used to override other packages)
Both approaches obviously need copious safety checks to make sure they are not breaking another override and hence giving unintended consequences.
Both will automatically lead to a 'black' classification for any such package in the marketplace, it it gets accepted to the marketplace at all. Many of the 'Related Projects' on http://www.concrete5.org/developers/open-source/... started out as marketplace submissions that were just a bit too black.
Copyright
Portland Labs
· All Rights Reserved
1. There is a method 'override core by package' (I forget the exact name, but searching the forums and howtos on that will get you to it).
2. Copy a file into the root override during package install (which can also be used to override other packages)
Both approaches obviously need copious safety checks to make sure they are not breaking another override and hence giving unintended consequences.
Both will automatically lead to a 'black' classification for any such package in the marketplace, it it gets accepted to the marketplace at all. Many of the 'Related Projects' on http://www.concrete5.org/developers/open-source/... started out as marketplace submissions that were just a bit too black.