Today I was thinking of more examples to help explain my previous email. Here is one example from the eclipse world:
Package: eclipse-jdt (3.8.0~rc4-1) - http://packages.debian.org/wheezy/eclipse-jdt dep: default-jre Standard Java or Java compatible Runtime or java5-runtime virtual package provided by default-jre, gcj-4.6-jre, gcj-4.7-jre, gcj-jre, openjdk-6-jre, openjdk-7-jre or java6-runtime virtual package provided by default-jre, openjdk-6-jre, openjdk-7-jre dep: eclipse-platform (>= 3.8.0~rc4-1) Eclipse platform without development plug-ins .. Therefore: $ apt-get install eclipse-jdt # eclipse-jdt 3.8.0~rc4-1 also installs eclipse-platform >= 3.8.0~rc4-1 With chunk releases for Carbon 4.2+ being backward compatible, could the same principle be applied: $ apt-get install wso2-as # wso2-as 5.0 also installs wso2-core-platform >= 4.20 On Sun, Jan 5, 2014 at 3:46 PM, chris snow <[email protected]> wrote: > Has anyone ever looked at creating native linux platform installers for > WSO2 products? For example: > > - DEB for debian based distros > - RPM for redhat based distros > > I've been thinking of how the tomcat package works on ubuntu where the > latest major version (e.g. 7) completely replaces the previous version. > > However, from what I understand, wso2 features require a certain "major + > minor version + minimum chunk" version of Carbon so there would need to be > a packaged version of Carbon for each supported Carbon release, for example: > > - wso2-carbon-core-42.deb > - wso2-carbon-core-50.deb > - wso2-carbon-core-51.deb > - etc > > However, products with a different "major + minor" version > wso2-carbon-core-42, wso2-carbon-core-50, and wso2-carbon-core-51 could > co-exist as they would be considered different packages (though ports would > need to be selected as to avoid clashing). With the approach, you could > perform the following to install 4.2.x and 5.0.x side by side: > > apt-get install wso2-carbon-core-42.deb > apt-get install wso2-carbon-core-50.deb > > An increase in the chunk version would cause the package to be upgraded > (much the same as apt-get upgrade). For example, version of > wso2-carbon-core-42.deb (version chunk 2) would upgrade a previous > installation of wso2-carbon-core-42.deb (version chunk 1). > > WSO2 products could be installed on top of the carbon core base as > features, where there the feature has a dependency on the appropriate > version of Carbon, for example: > > - wso2-as-52.deb would have a dependency on wso2-carbon-core-42.deb > (version chunk 1+) > > Does this approach make sense? Would it work? > > Many thanks, > > Chris > > > > -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
