Assuming that LAPP will be modified in the future and that at present we are discussing a "copy" of LAPP as today, would it not make sense to have a completely Bare system which simply includes whatever is in the current version of LAPP, and then goes on to modify it?
I can see that the TurnkeyLinux-apps/lapp is indeed quite Bare (and including the Base and Lapp plan in
But I can see that many Apps do not have a Plan under the common tree. Lets take Magento for a moment. Lets say I wanted a Magento App that is based upon Magento but which has significant changes. I would want to take ongoing changes to the Magento App, but I would also want to have 3 other downloads go in, and when the version changes, the general capability of the system would change. Moreover, if there were major changes to the Magento-App those would be automatically pulled and integrated to the changes I wanted to have.
Process question (including rather than modifying)
Assuming that LAPP will be modified in the future and that at present we are discussing a "copy" of LAPP as today, would it not make sense to have a completely Bare system which simply includes whatever is in the current version of LAPP, and then goes on to modify it?
I can see that the TurnkeyLinux-apps/lapp is indeed quite Bare (and including the Base and Lapp plan in
https://github.com/turnkeylinux/common/tree/master/plans/turnkey
----------
But I can see that many Apps do not have a Plan under the common tree. Lets take Magento for a moment. Lets say I wanted a Magento App that is based upon Magento but which has significant changes. I would want to take ongoing changes to the Magento App, but I would also want to have 3 other downloads go in, and when the version changes, the general capability of the system would change. Moreover, if there were major changes to the Magento-App those would be automatically pulled and integrated to the changes I wanted to have.
Esoteric process question perhaps.