sts.oxidforge.org"<mailto:dev-general@lists.oxidforge.org>
<mailto:dev-general@lists.oxidforge.org>
Betreff: V6 to big metapackages, what about suggests?
Hi all,
why do the meta-packages require a lot of optional stuff e.g. (demodata,
amazon-pay-sdk, amazonpay4oxid, payone, …)?
From a pe
+2 :)
Am 11.04.18 um 12:24 schrieb Tobias Merkl:
+1
*Von: *Jens Trant
*Datum: *Mittwoch, 11. April 2018 um 11:58
*An: *"dev-general@lists.oxidforge.org"
*Betreff: *V6 to big metapackages, what about suggests?
Hi all,
why do the meta-packages require a lot of optional
+1
Von: Jens Trant
Datum: Mittwoch, 11. April 2018 um 11:58
An: "dev-general@lists.oxidforge.org"
Betreff: V6 to big metapackages, what about suggests?
Hi all,
why do the meta-packages require a lot of optional stuff e.g. (demodata,
amazon-pay-sdk, amazonpay4oxid, payone, …
Hi all,
why do the meta-packages require a lot of optional stuff e.g. (demodata,
amazon-pay-sdk, amazonpay4oxid, payone, …)?
From a perspective of an EE user, it is not really handy to build a custom
composer.json with all the OXID components along the whole hierarchy and
dependencies (metapac
