On 7/25/2011 3:34 PM, Patrick Lists wrote:
My condition in that case was that you couldn't count on the RPM to work anyway once the distribution changes. So you'll likely be repeating that extra effort anyway.
Not sure what you mean with "once the distribution changes" but within a major CentOS/RHEL version (e.g. 5 or 6) there is a stable ABI so an update to the distro should not introduce issues. In my experience apps deployed on RHEL 5.1 work equally on 5.7. If they work crappy, hire better developers :)
The context for the issue was someone moving from 5.x to 6.x.
And of course your next install may be on a non-RPM based system, making any rpm-packaging effort moot.
So do people in the Windows world decide to *not* build msi packages because their PHB might decide to replace all Windows with RHEL/CentOS?
But wouldn't it be better if they actually did that instead of locking themselves into a single vendors system?
I have never seen that (the not building msi packages that is). And neither the reverse.
How do you deal with java apps in cross platform environments?