I wouldn't try and merge the two or kill
custom-portal completely. Here's what I would do:
- In the portal-xtra1 CONTROL file, note that it conflicts with custom-portal:
- Just add Conflicts: custom-portal
- Copy the bootstrap code from the custom-portal package into the portal-xtra1 package (basically the contents of the boot/ directory in there;
- Tweak the portal startup page in boot/2/config-ocontroller-si-rootfs.txt - the mom.hbbtv.portal entry as Chris has already noted - so that is loads the page you want at startup;
- Move your code up a level so that it sits directly within /mod/var/mongoose/html/portal if that makes sense for your code structure;
- Provide an empty plugins/ directory in the same location as custom-portal did;
- Get the existing plugin authors (oh, that's just me : ) to update their package so that it references the new jquery library that you bundle, or the one in /mod/var/mongoose/html/js, rather than the one that came with custom-portal, or provide the old jquery 1.4.2 library alongside yours.
That way, the two portals can continue to exist but only one can be installed at a time. When you first do this, people will need to remove
custom-portal in order to upgrade
portal-xtra1 because of the conflict statement and if they ever want to switch back they need to remove the latter first.