"landing page" data not created when app uses an external data package

[eduarddrenth]

[tuurma]

@eduarddrenth do I get you right, you expected choosing the landing page profile to create a separate data xar?

Fwiw, there is a data package profile to create a data package, though this is really meant as a one-off thing, because unlike Jinks apps, I personally don't see the benefit of any automated updates, data obviously will be project-specific.

[tuurma]

For the moment marking with wontfix, until we establish what (and if) needs to be done

[eduarddrenth]

Sorry, not clear enough. When you yourself start with a separate data package, the landing page will not be placed in it, this will cause an error when starting the app.

[tuurma]

Ok, so we're talking this scenario:

• jinks app with defaults.data pointing to a separate data package
• enabling landing page profile adds the data/landing to the app package, not the data package

To fix, the copy script could use the paths relative to the defaults.data configuration.

Needs caution, since jinks.json only has hashes for current application resources, there's risk of overwriting the customized landing in the data package. Simple solution would be to only copy to the data package if the data/landing subcollection there doesn't exist.